quote_metrics

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

With no annotations, the description carries the full burden for behavioral disclosure. It implies a read-only operation but does not explain semantics like 'last' (e.g., latest available), error handling, or any side effects. Minimal behavioral context is provided.

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, concise sentence with no unnecessary words. It is front-loaded with the core action, but it lacks additional structure or elaboration that might help an agent, though it earns its 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?

Given the tool has six parameters, no output schema, and no annotations, this brief description is completely inadequate. It does not explain return values, parameter prerequisites, or how it differs from the many sibling time-based quote tools, leaving agents underinformed.

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 description mentions 'metric names,' which aligns with the required 'names' parameter, but provides no details on the other five parameters (chain, rpcUrl, format, decimals, contractAddress). Schema coverage is 0%, and the description does little to compensate, leaving most parameters unexplained.

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 fetches the latest quotes for specified metric names, using the verb 'Get' and a specific resource. It distinguishes from sibling tools like quote_metrics_at_block and quote_by_ids by targeting 'last quotes' and 'metric names'.

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 provided on when to use this tool over the time-specific variants (quote_metrics_at_block, etc.) or quote_by_ids. It simply states the action without context or exclusions.

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