Sonar quote

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

Annotations already declare readOnlyHint and openWorldHint, and the description builds on that by adding the 'short-lived' nature and the exact output fields expected, including expiry. It does not contradict annotations and adds meaningful behavioral context beyond the structured hints.

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 a single, front-loaded sentence that states the action and enumerates the key return values without wasted words. It is easy to scan and immediately useful for tool selection.

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 helpfully enumerates the quote fields returned. Combined with rich parameter descriptions and safety annotations, the tool is reasonably complete, though the short-lived expiry duration and relationship to sibling quote tools are not explained.

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%, and the schema already thoroughly documents all parameters, including a clarifying note that maximumToleranceBps is not price impact. The description itself adds no parameter-level details, so it does not improve on the schema, but it also does not need to.

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 identifies the action ('Request a short-lived Sonar quote') and the target resource ('Strata market'), and lists concrete return fields. It is distinct from generic market-data tools, but it does not explicitly differentiate itself from sibling quote tools like strata_swap_quote or strata_exact_output_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 description implies when to use this tool: when a short-lived quote for a Strata market is needed. However, it provides no explicit guidance about when not to use it or which sibling quote tool to choose instead, especially since strata_swap_quote and strata_exact_output_quote are available.

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