get_deepxiv_pmc

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

The description indicates a read operation ('Read'), implying non-destructive behavior, but does not disclose any additional behavioral traits such as authentication needs, rate limits, or data source specifics beyond 'via DeepXiv'. With no annotations, the description carries the full burden but is minimal.

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, front-loaded sentence with no superfluous words. Every element contributes to understanding the tool's purpose.

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 (two parameters, read-only intent) and the presence of an output schema, the description is minimally adequate. However, it lacks differentiation from the similar sibling get_deepxiv_paper and offers no usage context, leaving gaps for an AI agent.

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 add meaning. It explains the 'full' parameter by mentioning 'metadata' (when false) and 'full structured content' (when true). The 'pmc_id' parameter is self-explanatory from the tool name, but the description compensates for the schema's lack of descriptions.

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 'Read PMC metadata or full structured content via DeepXiv,' specifying the verb, resource, and scope. It distinguishes the tool from siblings like get_deepxiv_paper by mentioning PMC, though not explicitly contrasting with it.

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, such as get_deepxiv_paper or search_deepxiv. It lacks context on prerequisites or typical use cases.

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