redmine_upload_attachment

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains that the tool reads a local file, posts it to Redmine's attachment API, returns a token, and is constrained by server configuration. It does not cover failure modes or permissions, but for a simple upload it provides substantial transparency.

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 front-loaded with the core purpose and then efficiently explains token usage and constraints. It is four sentences long and every sentence contributes meaningful information, though it could be tightened slightly.

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 upload tool with no annotations and no output schema, the description covers the essential workflow, server restriction, and how to consume the returned token. It lacks details about output format, error conditions, and authentication, but overall it is adequate for invoking the tool 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?

Schema description coverage is 0%, so the description must compensate. It clarifies that file_path should be an absolute path, but it does not explain the semantics of the optional filename or content_type parameters. These are left entirely to inference from their names, which is insufficient given the total absence of schema descriptions.

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?

States a specific verb and resource: 'Upload a local file to Redmine and get an attachment token.' It clearly describes the operation and outcome, and differentiates itself from the sibling redmine_upload_file by explaining the token's role in issue creation versus project Files module addition.

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?

Provides clear context on how to use the returned token, including passing it to redmine_create_issue, redmine_update_issue, or redmine_upload_file. It also gives a server-configuration constraint (REDMINE_UPLOAD_DIR), but does not explicitly state when not to use this tool or mention alternative attachment mechanisms.

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