futuros_b3

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

No annotations provided, but the description fully discloses that the tool returns honest information about the situation and alternatives rather than actual quotes due to licensing issues. It clearly sets expectations and warns about dependencies.

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?

Description is front-loaded with key purpose and warnings. It's slightly verbose (repeating the caveat about honest info) but every sentence adds value for a tool with data restrictions.

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's limited data availability and reliance on licensed sources, the description covers all necessary context: what it does, data source limitations, alternatives, and single parameter. Output schema exists, so return values need not be explained.

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 100% and provides complete parameter info (contract codes, defaults). The tool description does not add extra semantics beyond what's already in the schema, so baseline 3 is appropriate.

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 'retorna informações sobre futuros agrícolas da B3' and lists specific commodities (boi gordo, soja, milho, café). It also distinguishes from sibling tools by recommending spot price 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 says when to use the tool (for B3 futures) and when not ('Para preços spot use...') with specific sibling tool names. Also warns about data source licensing and potential HTTP 401 errors.

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