redmine_attachment_upload

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses the return value (upload token) and its intended use, which is helpful. However, it does not state that this is a write operation, any authentication requirements, potential size limits, or error behavior. The description adds some value but is not rich enough for a higher score.

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, tightly packed sentence that conveys the action, endpoint, return value, and next step. It is front-loaded with the core purpose and wastes no words. Every piece of information is essential and directly useful to an agent.

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 two-parameter tool with no output schema and no annotations, the description covers the essential elements: what it does, what it returns, and how to use the result. It lacks details like error handling or constraints, but the complexity is low and the provided workflow guidance is sufficient for an agent to invoke it correctly.

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 covers both parameters (filename and content_base64) with minLength constraints, but the description provides zero additional meaning about them. Schema description coverage is 0%, so the description must compensate, but it does not mention parameters at all. The parameter names are self-explanatory, but the description adds no clarification on format, encoding, or constraints beyond what the schema already states.

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: 'Upload a file to Redmine' and specifies the endpoint (POST /uploads.json). It also distinguishes from sibling attachment tools (get, download, delete, update) by focusing on the upload step and the token return. This is a specific verb+resource with no ambiguity.

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 gives clear context for when to use it (when you need to upload a file) and even explains the follow-up workflow ('attach via issue/wiki update using uploads array'). However, it does not explicitly mention when not to use it or name alternative tools, so it stops short of a 5.

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