ConvertHistoryQuery

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses concrete operational behavior: it is an OpenAPI interface requiring API Key authentication, requires a specific ACL permission, and has a global rate limit of 50/path/s. This is exactly the kind of auth and rate-limit context that helps an agent invoke the tool safely.

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 compact and front-loaded: one clear purpose sentence followed by three concise, high-signal bullet lines covering access, permission, and rate limit. Every sentence adds operational value with no filler.

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?

The description gives strong access and scope context, but it is incomplete for an agent that needs to call the tool correctly: index and limit semantics are absent, no output format is described, and there is no guidance on pagination or defaults. With no output schema, these gaps matter.

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 schema provides no descriptions for index, limit, or accountType, and the description only clarifies accountType via 'comma-separated accountType' and 'multiple wallet types'. Index and limit are left completely undocumented, so the description only partially compensates for the 0% schema coverage.

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 the tool queries 'all confirmed conversion records', specifying a concrete verb, resource, and scope. It does not explicitly differentiate itself from the many conversion-related siblings like QueryResult or QueryOrderByPage, so it falls just short of a 5.

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 the tool is for reading confirmed conversion history and notes prerequisites like API Key authentication and ACL permissions. However, it gives no explicit guidance on when to choose this tool over sibling conversion tools or when not to use it.

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