read_pdf_structure

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

No annotations, but description fully explains tool behavior: read-only extraction of structural content. Discloses what is returned but doesn't mention file locking or performance; still sufficient for a read tool.

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?

Description is well-structured: single sentence stating purpose, bulleted output details, and a usage directive. No redundant sentences; every part 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?

Given the output schema exists, description complements it by explaining output structure. Covers purpose, parameters, and usage. Could add edge-case behavior but overall adequately complete.

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 100%, so baseline is 3. Description adds no additional parameter meaning beyond what schema provides; it lists output fields instead of detailing input parameters.

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 clearly states verb+resource: 'Extract the complete structural content of a PDF document.' Details output (page dimensions, text elements with coordinates, fonts, color) and distinguishes from sibling modification tools.

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?

Explicit guidance: 'Use this tool FIRST to understand the document layout before making any modifications.' Implies alternatives are the sibling tools involving modifications.

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