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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context beyond those annotations: it returns a welcome message and example questions, and it specifies that the output should be relayed verbatim. This is sufficient for such a simple zero-argument tool.

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 front-loaded with the tool's purpose and then gives precise trigger conditions. It is somewhat long because of the exhaustive trigger list, but every element serves a practical purpose for an agent deciding when to invoke it. Minor redundancy exists in the repeated 'Ask AMZScout' capitalization examples.

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?

For a zero-parameter demo tool with no output schema, the description is complete: it states what the tool does, when to call it, what to expect back, and how to handle the output. Nothing needed for correct invocation is missing.

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 takes zero parameters, so there is nothing meaningful for the description to add beyond the schema. The baseline for a zero-parameter tool is 4; the description correctly avoids inventing unnecessary parameter details.

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?

The description clearly states a specific verb ('Start AMZScout') and its resource, along with the concrete result: a welcome message and example questions. This clearly distinguishes it from the sibling analysis/search tools, which perform data operations rather than greeting/demo behavior.

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?

It explicitly tells the agent when to call this tool: at the very start of the conversation and whenever the user greets or says triggers like 'Ask AMZScout', 'demo', 'begin', 'help', and similar phrases. It even clarifies case-insensitivity and instructs to relay output verbatim, which is actionable and unambiguous.

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