get_conversion

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

With no annotations, the description must fully disclose behavioral traits. It indicates a read-like operation (checking status) but does not explicitly state it is non-destructive, lacks side effects, or requires any permissions. The description is minimal and does not cover idempotency or potential errors.

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 concise with a single sentence that front-loads the status values. However, it could be structured to include parameter guidance or usage notes without adding length.

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 simple status-check tool with one parameter and no output schema, the description is adequate but incomplete. It misses guidance on the relationship to get_conversion_result and does not explain the parameter. The lack of annotations and schema descriptions increases the burden on the description, which it only partially meets.

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 only parameter, conversion_id, is listed in the schema but not described in the tool description, and the schema has no description. The description adds no meaning beyond the parameter name, leaving the agent to infer its format or source (e.g., from list_conversions).

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 checks a conversion's status and lists the possible statuses (queued, processing, completed, failed). It also mentions the additional per-account summary when completed. However, it does not explicitly differentiate from sibling tools like get_conversion_result, which may have overlapping functionality.

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 like get_conversion_result or list_conversions. There is no mention of prerequisites, context, or exclusions, leaving the agent without decision support for tool selection.

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