extract_local_pdf

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

No annotations are present, so the description carries the full burden of disclosing behavior. It only states that text is extracted; it omits whether the file is only read, what happens with unreadable or scanned PDFs, and how the required metadata parameters affect processing.

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 one-sentence description is efficient and front-loaded with the key action. It is not padded, though it is so minimal that it sacrifices useful behavioral context.

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 no output schema and no annotations, the description should clarify what the agent receives and any limitations. It does not explain return format, prerequisites for the local file, or the role of the required metadata parameters, leaving meaningful gaps for correct invocation.

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?

The schema documents all four parameters with descriptions and 100% coverage, so the baseline is 3. The description adds no parameter-level meaning, such as why symbol/country/documentType are required for local PDF extraction.

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 uses a specific verb ('extract') and a clear resource ('local PDF file'), making the operation immediately understandable. It is also clearly distinct from the sibling tools, none of which perform raw PDF text extraction.

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?

There is no when-to-use guidance, prerequisites, or mention of alternatives. The agent has to infer that this tool is for pulling raw text before IR summarization or analysis; the description does not state that context.

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