zotero_get_pdf_outline

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

Despite no annotations, the description covers key behaviors: returns markdown list, handles missing outlines gracefully, is read-only, works in both local and web modes, and lists a dependency (PyMuPDF).

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?

Compact and well-structured: purpose first, then usage guidance, parameter details, scope, dependency, and example. Each sentence adds value without 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?

Given the tool's simplicity (one parameter, clear output), the description covers all necessary aspects: purpose, usage, parameter, edge case, scope, and dependencies. Output schema exists but format is already described.

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?

Single parameter item_key is thoroughly explained: accepts both attachment and parent keys, with automatic resolution. Includes an example call. Compensates for 0% schema coverage.

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?

Clearly states 'Extract the table of contents from a PDF attachment' with output format specified. Distinguishes from sibling tools like zotero_get_item_fulltext by positioning it as a lighter alternative.

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 advises using before fulltext, notes outline is typically under 200 tokens, provides alternative tool (zotero_get_item_children) for finding the correct key, and specifies scope (PDFs only, not EPUBs).

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