Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description states it returns a welcome message and example questions, and instructs to relay output verbatim. While the readOnly annotation is present, the description adds context about the output and handling, which is useful for the agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise enough, though it repeats the trigger examples. It is not overly verbose and is structured in a single clear sentence, which is acceptable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple nature (no params, no output schema), the description fully covers what the tool does, when to use it, and how to handle its output. No additional information is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline is 4. The description does not need to explain any parameter details, and the empty schema is fully covered.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it returns a welcome message and example questions, and explicitly distinguishes itself from other AMZScout tools by its demo/greeting purpose. The name 'amzscout_demo' is reinforced by the description, making its function unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit usage triggers: call at the very start of conversation, on greetings, or when user says specific phrases like 'Ask AMZScout', 'demo', 'begin', etc. This leaves no ambiguity about when to invoke the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.