delete_attachment

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

Annotations already indicate destructiveHint: true and readOnlyHint: false, so the destructive nature is known. The description adds the requirement for WRITE_ENABLED, which is helpful context. However, it does not disclose other potential behaviors like irreversibility or cascading effects.

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 extremely concise: a single sentence that conveys the purpose and a key requirement. There is no wasted text, and it is front-loaded with the core action.

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?

For a simple delete operation with one parameter, the description covers the basic purpose and a critical prerequisite. It lacks detail about return values or error handling, but given the simplicity and no output schema, it is nearly complete.

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 single parameter attachment_sys_id has full schema coverage in the input schema (description: 'sys_id of the attachment to delete'). The description does not add any additional meaning or context beyond what the schema already provides. Baseline 3 is appropriate.

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 'Delete an attachment from a record', specifying the action (delete) and resource (attachment from a record). It distinguishes from sibling tools like upload_attachment and list_attachments by the delete action and the required WRITE_ENABLED condition.

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 mentions a requirement (WRITE_ENABLED=true) but does not provide guidance on when to use this tool versus alternatives (e.g., when not to use it, or to use get_attachment_metadata or upload_attachment instead). There is no explicit context for selection.

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