extrair_pdf

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

No annotations provided; description adds caching behavior but does not disclose error handling, auth needs, or limitations (e.g., only works with text PDFs). Adequate but not thorough.

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, front-loaded with purpose, no fluff. Every sentence adds value (purpose, caching, combination advice). Excellent structure.

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?

With schema covering parameters and no output schema, description includes caching and combination hint. Lacks output format details, but is fairly complete for a simple extraction tool.

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 100% with descriptions; description adds no extra parameter meaning. Baseline 3 is appropriate as schema does the heavy lifting.

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 verb 'extrair' and resource 'PDF', specifies it extracts full text, and distinguishes from siblings by mentioning caching and combination with buscar_nos_artigos. No ambiguity.

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 'use this tool to get raw content' and suggests combining with buscar_nos_artigos for excerpts. Lacks explicit when-not-to-use or prerequisites, but provides clear context.

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