SmallAssetConvert

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

With no annotations, the description carries full burden. It discloses the async nature, required API key permission ('Convert'), rate limit (5/s), and load balancing strategy (consistent hash). This goes beyond basic purpose and helps agents understand operational constraints and post-invocation expectations.

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 concise: one sentence for the core action, followed by three bullet points for async behavior, permission, rate limit, and load balancing. Every sentence adds value without redundancy, making it easy for an agent to parse key information quickly.

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 no output schema, the description covers the tool's lifecycle well: input (quoteId from get-quote), async execution, and post-invocation action (check Get Exchange History). It also provides permission and rate limit context. Minor omission: no indication of immediate response structure or common failure modes, but acceptable for a tool with one parameter.

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 sole parameter 'quoteId' has no schema description (0% coverage), but the description adds significant meaning by specifying it must come from the get-quote interface. This provenance guidance compensates for the schema gap and helps agents correctly source the value.

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 confirms and executes small asset conversion using a quoteId from the get-quote interface. This verb+resource combination is specific and distinguishes it from sibling tools like SmallAssetQuote (which generates quotes) and ConvertExecute (likely a general conversion tool). The async nature and status check instruction add precision.

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 explicitly instructs users to obtain a quoteId from the get-quote interface and to check final status via the Get Exchange History endpoint. This provides clear context on when to use and what to do after invocation. It does not explicitly mention when not to use or list alternatives, but the workflow implication is strong.

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