vera_rates

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

With no annotations, the description adds limited behavioral context: a 5-minute cache and a cost of $0.02 USDC via x402. However, it does not disclose whether the operation is read-only, idempotent, or requires authentication.

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?

Three sentences with no redundancy. Front-loads purpose, lists outputs, then adds caching/pricing. Every sentence adds unique value.

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 and 0% parameter documentation, the description lacks details on return format, error handling, and the 'signals' parameter. It covers the core purpose but leaves gaps for an agent to invoke correctly.

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?

Schema coverage is 0%, so the description must compensate. It explains the 'country' parameter via its enum values, but the 'signals' parameter is completely ignored – no hint what values or purpose it serves.

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 returns real-time central bank rates for specific LATAM countries and lists the exact rate names (TRM, DTF, IBR, TIIE, Selic, UF). It distinguishes itself from sibling tools like 'vera_context' or 'vera_entity' by focusing solely on rate retrieval.

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 explicit guidance on when to use this tool versus alternatives. The description implies usage for LATAM country rates but does not explain when not to use it or mention sibling tools for context or sanctions.

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