zotero_get_pdf_outline

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

Despite no annotations, the description fully discloses behavior: read-only, dual key acceptance, automatic resolution, error message for missing outline, and output format. This compensates for lack of structured metadata.

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 detailed but every sentence adds value. It is front-loaded with the core purpose, followed by usage guidance and specifics. Slightly longer than minimal but remains efficient.

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?

Covers return format, error case, prerequisites, scope, and key acquisition. Given the tool's simplicity, the description is fully complete for effective use.

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?

With 0% schema coverage, the description adds substantial meaning: item_key can be attachment or parent key, automatic resolution, and guidance to find correct key via sibling tool. Example provided.

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 clearly states the tool extracts a table of contents from a PDF attachment as a hierarchical markdown list. It distinguishes from sibling 'zotero_get_item_fulltext' by contrasting token sizes and mentions handling of missing outlines.

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 when to use ('orient in a paper before calling fulltext'), when not to use ('EPUBs have no outline extraction'), and how to find the correct item key via sibling tool. Also notes read-only nature and installation prerequisite.

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