extract_metadata

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Extract' implies a read-only operation, but the description does not specify what metadata fields are returned, whether the file parameter accepts a path or base64, or any side effects. This is minimal and vague.

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 short (one sentence), but it is under-specified rather than concisely effective. It lacks critical information that should accompany a one-sentence description, such as output format or parameter handling. Similar to the 'Process' example, this is over-simplification without substance.

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?

Despite the tool being simple (1 parameter), the description does not provide enough context about what 'comprehensive metadata' includes or how the file input is supplied. While an output schema exists, the absence of any parameter description and annotations leaves the tool incomplete for an agent to invoke correctly.

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% and the only parameter 'file' has no type or description in the input schema. The description 'PDF metadata' does not explain how the file should be provided (e.g., local path, URL, base64), nor does it add any parameter-level semantics. This is a critical gap.

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 'Extract comprehensive PDF metadata' clearly states the action (extract) and resource (PDF metadata), and uses 'comprehensive' to suggest thoroughness. However, it does not explicitly distinguish itself from the sibling tool 'get_pdf_info', which likely serves a similar purpose, so it falls short of a 5.

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 is provided on when to use this tool versus alternatives like get_pdf_info or extract_text. The description does not mention prerequisites, target users, or scenarios, leaving the agent to infer usage solely from the name.

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