Inspect PDF metadata

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. Description adds meaningful behavioral context: what data is inspected (version, page count, etc.) and how check assertions work (checksPassed=true only when all checks hold). No contradiction.

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?

Single paragraph but information-dense and front-loaded with purpose. Could benefit from bullet points for the listed attributes, but no redundant sentences; every sentence earns its place.

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 output schema present, description doesn't need to explain return values. Covers all key aspects: inspection scope, check assertions behavior, and parameter intent (though pages parameter is brief but schema covers it). Complete for a read-only inspection 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%, baseline 3. Description adds value by detailing the meaning of check array values ('pdfa', 'signed', etc.) and explaining the checksPassed flag, which goes beyond the schema description.

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 starts with 'Read-only inspection of an existing PDF' and lists specific attributes (version, page count, encryption state, etc.) and the check array for assertions. Clearly distinguishes from sibling tools that modify or generate PDFs.

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 describes the check array for CI-style assertions and explains checksPassed logic. Context of sibling tools (all mutation or generation) makes inspection use case clear, though no explicit when-not-to-use guidance.

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