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

The readOnlyHint and destructiveHint annotations already cover the safety profile, so the description only needs to add behavioral context. It adds 'live' and 'published SDK quote route,' but does not disclose result semantics, pagination, rate limits, or quirks. No contradiction with annotations.

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?

One sentence contains the action, target, and scope with no wasted words. The key differentiator, 'across platforms,' is placed immediately after the verb.

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?

With no output schema, the description should indicate what the tool returns, such as quotes per platform, availability, or best price, but it is silent on return shape. The six-parameter schema, including a raw nested params object, needs more guidance on how fields drive the comparison and which sibling tools should be used instead.

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?

Schema description coverage is 100%, so the baseline is 3 even though the tool description omits parameter details. The schema's descriptions are terse but present, and the description adds no parameter-level meaning beyond what the schema already provides.

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 names a specific action (compare), a distinct resource (live quote availability), and a scope (across platforms). This clearly differentiates it from closely related siblings like peer_quote, which appears to target a single quote.

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?

The cross-platform phrasing implies when this tool is appropriate, but it does not explicitly name alternatives or give when-to-use/when-not-to-use guidance. Given the large sibling set containing other quote/market tools, explicit routing would materially help.

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