redmine_attachments

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

The description does not disclose side effects (e.g., 'delete' is destructive, 'get' is read-only) or permissions required. With no annotations, the description fails to specify behavioral traits beyond the action names.

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 brief but lacks structure. It does not front-load critical information such as required parameters or usage context, sacrificing utility for brevity.

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 complexity (6 parameters, nested objects, no output schema), the description is severely incomplete. It omits explanations for pagination, error handling, return values, and practical usage patterns.

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 description adds no parameter details beyond the schema. Despite 50% schema coverage, it does not elaborate on parameters like 'attachment_id' or 'action', leaving their interpretation to the agent.

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 states 'get, delete' which identifies actions on attachments, but it fails to clarify what 'get' returns (e.g., file content or metadata). The phrasing 'Manage attachments' is vague, and the tool's purpose is not sharply differentiated from other Redmine tools.

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?

No guidance is provided on when to use this tool versus siblings, nor instructions on how to choose between 'get' and 'delete'. There is no mention of prerequisites, authentication needs, or pagination handling.

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