redmine_delete_attachment

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

No annotations are provided, so the description must disclose behavior. It says 'Delete', implying destructive action, but it does not mention permissions, side effects (e.g., cascading deletions), or error conditions. The behavioral insight 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 extremely short (one sentence). While it is not verbose, it is under-specified. Every sentence earns its place, but more structure or detail would improve clarity.

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?

With low complexity (1 parameter) and no output schema, the description should still explain the outcome (e.g., success response, error handling). It fails to provide a complete picture, leaving the agent uncertain about invocation results.

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% description coverage for the single required parameter 'id', which is described as 'Attachment ID to delete'. The description adds no further meaning beyond what the schema already provides.

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 'Delete' and the resource 'attachment from Redmine'. It distinguishes from sibling tools like 'redmine_get_attachment' and 'redmine_update_attachment' by specifying the deletion action, though it does not elaborate on unique scope.

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?

There is no guidance on when to use this tool or when to avoid it. No alternatives are mentioned, such as 'redmine_update_attachment' for modifying attachments or 'redmine_delete_issue' for deleting related items. The description provides no usage context.

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