classify_document

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

The description discloses a concrete side effect: 'Saves classified_document.json' and references an external PDF4me API. However, it doesn't mention authentication, whether the input PDF is modified, or error behavior. Since no annotations exist, this limited transparency leaves gaps for a mutation-like 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?

The description is a single, well-structured sentence that front-loads the action, then lists parameters and the output file. Every phrase carries information, with 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?

The tool has no output schema, annotations, or parameter descriptions. The description provides minimal context, omitting details on classification result structure, use cases, and behavioral constraints, making it incomplete for an agent to fully understand the 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?

The description merely repeats parameter names from the schema ('pdf_file_path; optional request_doc_name and output_dir') without explaining their meaning or usage. With 0% schema description coverage, this is insufficient to guide correct invocation.

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 action ('Classify a PDF by content') and references a specific API endpoint. It distinguishes from siblings like process_invoice or parse_document by indicating generic classification, but doesn't elaborate on what classification outputs are produced.

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?

The description provides no guidance on when to use this tool versus alternatives such as parse_document or process_*. It lacks use cases, prerequisites, or exclusions, leaving the agent to infer the appropriate context.

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