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

The phrase 'would return right now' implies a simulated quote rather than an actual execution, which adds context beyond the readOnlyHint annotation. However, no other behavioral details such as error handling or rate limits are disclosed.

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 a single, efficient sentence with no wasted words. However, its brevity under-specifies the tool's behavior and parameters, making it minimally adequate in structure.

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?

The description is far from complete. It lacks parameter explanations, return value details, and any caveats, which is especially problematic given the tool has four parameters and no output schema.

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?

With 0% schema description coverage, the description must explain the parameters, but it does not mention tokenIn, tokenOut, amountIn, or slippageBps. No meaning is added beyond the bare schema property names.

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 provides a quote for a trade between USDG and a stock, using a specific verb ('return') and resource. It is distinguishable from siblings like metamuse_price by mentioning the trade context, though it does not explicitly name alternatives.

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?

No guidance is given on when to use this tool versus siblings like metamuse_price or metamuse_assets. There are no exclusions or conditions provided, leaving the agent to infer usage context.

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