convert_qu_usd

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the use of 'current live price' but does not explain what happens if both qu and usd are provided, if neither is provided, or what the output format looks like. These are significant ambiguities for a conversion tool.

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 two succinct sentences that front-load the primary action ('Convert between QU and USD') and then explain the two usage modes. There is no fluff or redundant repetition of schema details.

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?

While the tool is simple, the description does not explicitly require exactly one parameter or describe the return value structure. Since there is no output schema, the description should compensate for these gaps. It provides a minimum viable explanation but lacks some important behavioral specifics.

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 input schema already describes both parameters with 100% coverage, so the baseline is 3. The description adds value by indicating the 'either/or' exclusivity of the parameters, which is not expressed in the schema. This helps the agent understand that exactly one should be specified.

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 converts between QU and USD using the current live price. The verb 'Convert' and the explicit resource pair distinguish it from sibling tools like get_token_price, which focuses on price data rather than conversion.

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 gives clear usage context by saying 'Specify either a QU amount... or a USD amount', which tells the agent how to structure the input. However, it does not explicitly mention alternatives or when not to use the tool, so it stops short of full guidance.

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