Extract the full text of an item's PDF

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

Annotations already mark this as read-only and non-destructive. The description adds valuable behavior: the attachment is downloaded through the Zotero API and parsed locally, and the return value includes a provenance header. This goes beyond the annotations and helps the agent anticipate network dependency and output characteristics.

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 well-structured and compact, with the core purpose front-loaded, a short behavioral note, and clearly separated Args and Returns sections. Every sentence earns its place; there is no filler or 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?

The description is complete for a read-only extraction tool: it covers all three parameters, the return format, and key behavioral context. The output schema exists, so the return-value structure does not need to be spelled out, and the safety profile is already covered by annotations.

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%, so the description must fully explain parameters. It does: item_key can be the parent item or the attachment itself; pages includes concrete format examples and default behavior; max_chars is explained as overriding the configured character cap. This adds substantial meaning beyond the raw schema.

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 opens with a specific verb and resource: 'Extract readable text from the best attachment of an item.' It clearly distinguishes itself from siblings that retrieve metadata, children, or annotations, and clarifies that the output is the document's own text, not a summary.

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?

The context is clear: an agent should use this tool when it needs the full readable text of an item's PDF attachment. It does not explicitly name alternatives or exclusion criteria, but the purpose is unambiguous enough to guide selection among the sibling tools.

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