cotacao_boi_gordo

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

With no annotations, the description covers the fallback mechanism and data sourcing. It discloses that it uses Scot Consultoria as primary and ESALQ/B3 as fallback, adding transparency beyond a simple read operation.

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?

Two sentences, no filler. Front-loaded with purpose, followed by source details. Every sentence contributes essential information.

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 simple tool with one parameter and an existing output schema, the description is fully adequate. It covers data sources and fallback, leaving no critical gaps.

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 has 100% coverage for the single parameter. The description adds value by explaining the fallback behavior if the praça is not found, which the schema does not address.

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?

Description clearly states it returns the quotation of boi gordo for a Brazilian regional market. It distinguishes from sibling tools like cotacao_leite and cotacao_milho by specifying the commodity. The mention of primary and fallback sources adds clarity.

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?

Description implies when to use (for boi gordo quotes) but does not explicitly state when not to use or name alternatives. The fallback behavior provides context on handling missing parameters, which is helpful.

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