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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by detailing the exact data returned (dólar, maíz, novillo, spread, arrendamiento) and explaining the spread as a profitability proxy. No contradictions with annotations.

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 sentence (with semicolons) that front-loads the purpose and lists data items concisely. No wasted words; every part adds 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, the description fully specifies what the tool returns: all major market indicators and their units. It also explains the spread's meaning as a profitability proxy. With sibling tools, it is clear how this tool fits into the ecosystem.

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?

No parameters exist; schema coverage is 100% (vacuous). The description confirms 'sin parámetros', which is necessary for the agent to know it's a zero-argument call. Baseline for 0 params is 4, and the description meets that.

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 it provides macroeconomic context ('Contexto macro del mercado ganadero argentino'), lists specific data points (dólar blue y oficial, maíz FOB, novillo INMAG, spread, índice de arrendamiento), and explicitly distinguishes from sibling tools by naming what it does not provide (serie INMAG, precios por categoría) and pointing to 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?

Explicitly states 'sin parámetros' (no parameters) so the agent knows it can be called directly. It also says what it does NOT do and provides alternative tool names (→get_indice_novillo, get_precios_hacienda), giving clear when-to-use and when-not-to-use guidance.

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