edit_attachments

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

With no annotations provided, the description carries the full burden of explaining side effects. It says 'remove' but does not disclose whether the original PDF is modified, whether output_name creates a new file, what happens when files are removed, or what the list output looks like. This is insufficient for a mutating 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 concise sentence that front-loads the verb and resource. No unnecessary words or repetition are present.

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?

This is a 4-parameter mutation tool with no annotations and no output schema. The description fails to explain the overall workflow, such as how 'remove' interacts with the 'remove' array and 'output_name', whether the original file is altered, or what a successful listing/removal returns. The provided schema details parameters but not the operational 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 100% coverage with descriptions for all four parameters, including the action enum, remove list, and output_name. The description adds no extra parameter-level meaning, so the schema itself does most of the work, warranting the baseline score.

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 function: listing or removing file attachments in a PDF, using specific verbs and a resource. It is readily understandable, though it does not explicitly distinguish from sibling tools like add_attachments or extract_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 based on the actions 'list' and 'remove', and the sibling tool names give context, but it does not explicitly state when to use this tool over alternatives or when not to use it. No alternative tools are mentioned.

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