QuerySmallAssetConvertOrder

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

Annotations already mark this as read-only, and the description adds useful operational behavior: the required API key permission ('Convert') and rate limit (10/s). It also clarifies the paginated and history-oriented nature of the call. No conflict with the 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?

The description is compact and front-loaded with the core purpose, followed by two concise operational facts. There is no redundant or filler content.

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 6-parameter read-only tool with no output schema, the description covers high-level pagination, filtering, permission, and rate limiting. It does not explain accountType filtering or cursor/pagination mechanics, so an agent would need to infer or discover these details before invoking with confidence.

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 description maps 'order number' and 'time range' to likely parameters (quoteId, startTime, endTime), adding meaning absent from the schema. However, schema description coverage is 0%, and the description does not address accountType, size, or cursor semantics, leaving a meaningful portion of the input surface unexplained.

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 tool as a 'Paginated query of small asset conversion history records' and states its filtering capabilities. It distinguishes the resource at the 'small asset' level from general conversion history tools, though it does not explicitly call out related siblings like ConvertHistoryQuery.

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 the tool: when querying small asset conversion history, optionally filtered by order number and time range. However, it provides no explicit guidance on when not to use it, nor does it name alternative tools for different conversion scenarios.

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