remove_paper

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

With no annotations, the description carries the burden of disclosing behavioral traits. It mentions optional Zotero deletion but does not describe irreversibility, side effects, or the impact of the 'dry_run' parameter. The description provides some context but lacks comprehensive transparency.

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?

A single sentence with no wasted words. It is concise but could benefit from additional details without becoming verbose.

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 an output schema exists, return values are covered. However, the description omits details about the 'dry_run' parameter and the format of 'identifier'. It covers the main action but not the full context 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?

The schema has 0% description coverage, so the description must compensate. It only explains the 'include_zotero' parameter indirectly ('optionally deleting its Zotero item'). The 'identifier' and 'dry_run' parameters are not mentioned, leaving significant ambiguity.

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 action ('Remove a paper from the vault') and the optional deletion of the Zotero item. This distinguishes it from sibling tools like 'move_paper' or 'add_paper'.

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 indicates a clear use case (removing a paper) and mentions the option to delete the Zotero item. However, it does not explicitly state when to use this tool versus alternatives, such as 'move_paper' or 'mark_paper'.

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