QueryResult

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

The description discloses authentication method, ACL permission, and rate limit, which are useful behavioral traits beyond what annotations might provide. However, it does not describe the nature of the results (e.g., format, pagination, filtering) or confirm read-only behavior, leaving gaps.

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 three sentences, front-loaded with purpose, followed by auth and rate limit details. It is compact but could be slightly more efficient by omitting redundant info like 'OpenAPI interface'.

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 lack of output schema and annotations, the description should provide more context about the tool's return value, usage context, and differentiation from siblings. It covers only auth and limits, leaving the agent underinformed.

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 input schema has two required parameters with no descriptions, and the description does not explain their meaning or valid values. Since schema coverage is 0%, the description should compensate but fails to do so.

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 states 'Query cryptocurrency exchange results using a quote transaction ID,' which clearly identifies the tool's action and resource. It distinguishes from many sibling tools that are also query-like, but does not precisely define what 'exchange results' means, leaving some ambiguity.

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 provides no guidance on when to use this tool versus alternatives. It lists authentication and rate limits but does not mention when this tool is appropriate or what distinguishes it from similar tools like getQuotes or queryTrade.

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