document

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

No annotations provided, so description carries full burden. It does not disclose that the tool dispatches based on the 'op' parameter, nor any side effects, authentication needs, or behavioral traits. Complete lack of transparency.

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, but they provide minimal value. First sentence is vague, second seems irrelevant to usage. While short, it is not effectively concise because it wastes space on unhelpful information without providing core purpose or direction.

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 complexity (26 parameters, required 'op'), the description is extremely insufficient. No output schema. The agent cannot infer what operation to perform or how parameters relate. Completely inadequate.

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 0%. The description adds no meaning to the 26 parameters. It only says 'Consolidated PDF document entrypoint', giving no hints about what parameters like 'op', 'file_paths', 'pdf_path', etc. do.

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 states 'Consolidated PDF document entrypoint' but does not specify operations or actions. The name 'document' is generic, and with numerous sibling tools for specific document tasks, this description fails to distinguish what this tool does that others don't. It's vague and essentially a tautology.

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?

No guidance on when to use this tool versus alternatives. The mention 'Existing document tools stay registered and keep their original contracts' implies a consolidated entrypoint but does not clarify when to prefer this over other document tools or how it differs.

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