get_convert_status

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It does not mention safety (read-only vs. destructive), required permissions, rate limits, or error states. The name implies a read operation, but this is not explicitly stated.

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 very short (one sentence plus parameter list), which is efficient but lacks necessary detail. It earns its place without wordiness, but the brevity sacrifices completeness.

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?

Without output schema or annotations, the description should explain the return value (e.g., status enum, additional fields). It also fails to differentiate from numerous sibling tools of similar naming pattern (e.g., get_fiat_convert_status, get_convert_history). The tool is simple but still requires more context for effective use.

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 0%, so the description must compensate. It only adds bare labels ('Quote transaction ID', 'Account type') without explaining format, allowed values, or source. For example, 'quote_tx_id' likely comes from request_convert_quote, but this is not mentioned.

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 'Get crypto-to-crypto conversion status,' which is a specific verb+resource combination. It distinguishes from siblings like get_convert_history (history of conversions) and confirm_convert_quote (confirm action) by focusing on status retrieval.

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 does not mention prerequisites (e.g., having a quote_tx_id from request_convert_quote) or situations where other tools like get_convert_history would be more appropriate.

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