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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose behavioral traits such as error handling (e.g., invalid paths, corrupted files), performance characteristics (e.g., large file handling), or output format details beyond 'full text' (e.g., encoding, structure).

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 a single, efficient sentence with zero waste—it directly states the action, source, and output. It is appropriately sized and front-loaded, making it easy to parse quickly.

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 low complexity (1 parameter, no nested objects) and the presence of an output schema, the description is minimally adequate. However, with no annotations and incomplete behavioral disclosure, it lacks details on error cases or usage constraints that would enhance completeness.

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?

The description adds meaning beyond the input schema by specifying that 'local_path' refers to a 'local file path' for a PDF file, which clarifies the parameter's purpose since schema coverage is 0%. However, it doesn't detail format requirements (e.g., absolute vs. relative paths, file extensions).

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 specific action ('Read a PDF file') and resource ('from the local file path'), distinguishing it from sibling tools like 'zotero_read_pdf' which likely interacts with Zotero library PDFs rather than local files. It provides a complete verb+resource+scope statement.

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 description provides no guidance on when to use this tool versus alternatives like 'zotero_read_pdf' or other PDF processing tools. It mentions the source ('local file path') but doesn't specify prerequisites, limitations, or comparative contexts with siblings.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a retrieval operation, implying read-only behavior, but doesn't cover aspects like authentication needs, rate limits, error handling, or what happens if the itemKey is invalid. This leaves significant gaps for an agent to understand the tool's behavior.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it highly concise and well-structured.

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 low complexity (1 parameter) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers the basic operation but lacks details on usage context and behavioral traits, which are partially mitigated by the output schema.

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?

The schema description coverage is 0%, so the description must compensate. It mentions 'itemKey' as the parameter, adding meaning beyond the bare schema, but doesn't explain what an itemKey is, its format, or where to find it. This provides some context but is insufficient for full understanding, aligning with the baseline for partial compensation.

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 verb ('Retrieve') and resource ('details of a specified item in the Zotero library'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'zotero_search_items' (which likely searches rather than retrieves by key), so it doesn't reach the highest score.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'zotero_search_items' for searching or 'zotero_read_pdf' for reading PDFs, nor does it specify prerequisites or contexts for retrieval by itemKey.

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

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: it finds the first PDF attachment (implying it may skip others), reads from the local file system (suggesting file access requirements), and returns full text. However, it lacks details on error handling (e.g., if no PDF exists), permissions needed, or performance aspects like rate limits. It adds value but is not comprehensive.

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 a single, well-structured sentence that front-loads the core action and resource. It efficiently covers the tool's purpose, parameter context, and outcome without any wasted words. Every part earns its place by contributing essential information.

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 moderate complexity (involving file system access and PDF parsing), no annotations, and an output schema (which handles return values), the description is mostly complete. It explains what the tool does and the parameter's role. However, it could improve by mentioning potential failures (e.g., no PDF found) or dependencies, but the output schema likely covers return structure, so it's adequate.

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?

The input schema has 0% description coverage, providing no details about 'itemKey'. The description fully compensates by explaining that 'itemKey' specifies the item in the Zotero library whose children are searched for PDF attachments. This adds crucial meaning beyond the bare schema, making the parameter's purpose and usage clear.

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 specific action ('find the first PDF attachment, read it from the local file system, and return its full text') and the resource ('children of the item specified by itemKey in the Zotero library'). It distinguishes from sibling tools like 'read_pdf' (general PDF reading) and 'zotero_get_item'/'zotero_search_items' (item retrieval/search) by focusing on PDF extraction from Zotero attachments.

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 description implies usage when you need to extract text from a PDF attached to a Zotero item, but it does not explicitly state when not to use it or name alternatives. For example, it doesn't clarify if 'read_pdf' should be used for non-Zotero PDFs or if 'zotero_get_item' is better for metadata-only access. The context is clear but lacks explicit exclusions.

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

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it excludes attachments and limits results to 30. However, it doesn't cover important aspects like whether this is a read-only operation, error conditions, rate limits, or authentication needs, leaving gaps for a search 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?

The description is a single, efficient sentence that front-loads the core purpose and includes key constraints. Every word earns its place with no redundancy or unnecessary details.

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 moderate complexity (search operation with constraints), no annotations, and an output schema (which reduces need to describe return values), the description is partially complete. It covers the search scope and limits but misses parameter details and broader behavioral context.

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?

The input schema has 1 parameter with 0% description coverage, and the description doesn't explain the 'q' parameter's semantics. It mentions searching by author and title, but doesn't clarify how 'q' relates to this or what format it expects. The description fails to compensate for the low 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?

The description clearly states the tool's purpose: searching items in a Zotero library by author and title. It specifies the resource (Zotero library) and action (search), but doesn't explicitly differentiate from sibling tools like 'zotero_get_item' or 'zotero_read_pdf' beyond mentioning it's a search operation.

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 description implies usage context by stating it searches by author and title, excludes attachments, and returns up to 30 results. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'zotero_get_item' or 'zotero_read_pdf', nor does it mention any exclusions or prerequisites.

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