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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds behavioral specifics: returns last business day data, min/avg/max in ARS/kg live weight + heads. No contradictions. Minor gap: no mention of pagination or limits, but acceptable given safety 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?

Concise single sentence with front-loaded purpose. Every clause adds value: source, examples, sibling differentiation, parameter details. No redundancy.

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?

Without an output schema, the description provides sufficient detail on return values (examples, min/avg/max, units, time). The sibling context is clear. Could mention if results are limited to one day, but 'último día hábil' implies that.

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 description coverage is 0%, but the description fully explains the sole optional parameter 'grupo': its enum values and behavior when omitted ('sin filtro, todas'). This adds significant meaning beyond the schema.

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 detailed prices by subcategory from MAG/Cañuelas for the last business day, with examples and units. It explicitly distinguishes from sibling tools: more granular than get_precios_hacienda and not the daily INMAG index.

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?

It explicitly compares to get_precios_hacienda (categories) and get_indice_novillo (index), guiding when to use this tool. The optional group parameter is explained. Could include when not to use, but the differentiation is sufficient.

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