Connect live Amazon data (optional)

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the bar is lower, yet the description adds useful behavior: this is an explanation-only tool, it is conditionally visible depending on token state, and it is not a prerequisite for the settlement workflow. It doesn't detail what the returned content looks like (steps? a URL?), which keeps it from a 5.

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?

A single sentence with the scope, the visible-condition, and the exemption clause packed in, and the most decision-relevant information (what data it unlocks) is front-loaded. No filler or restatement of the title.

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 parameterless, output-schema-less informational tool, the description covers what it does, when it appears, and what it does not affect. The only residual gap is whether invoking it starts an OAuth-style flow or just returns setup text — an agent might want that to set user expectations.

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 and the schema is an empty object, so there is no parameter meaning to convey. Baseline 4 applies; the description correctly avoids inventing inputs.

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 uses a specific verb ('Explains how to add') plus a concrete resource ('live Amazon data (orders, ads, stock, account health)') and explicitly separates itself from the settlement tools. An agent can tell this is an informational/setup tool rather than a data-retrieval tool without opening anything else.

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 gives a clear activation condition ('Listed only while no AGENTXRAY_TOKEN is set'), labels itself optional via the title, and states the exclusions ('the settlement tools do not need it'). What's missing is an explicit instruction like 'call this when the user asks for live orders/ads/stock data' — the routing is strongly implied rather than spelled out.

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