MCP Server for Lychee Redmine

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

No annotations are provided, so the description carries full burden. It discloses that partial updates are supported, which is useful behavioral context. However, it doesn't mention authentication requirements, rate limits, error conditions, whether changes are reversible, or what the response looks like. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 - just two sentences that directly convey the core functionality. Every word earns its place: first sentence establishes purpose, second adds crucial behavioral detail about partial updates. No wasted words or unnecessary elaboration.

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 this is a mutation tool with 7 parameters, 0% schema description coverage, no annotations, and no output schema, the description is insufficient. It covers the basic operation and partial update feature but lacks information about authentication, error handling, response format, parameter meanings, and relationships with sibling tools. The agent would struggle to use this tool effectively without additional context.

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 mentions 'only specify fields to change' which explains the partial update behavior, but doesn't provide any semantic information about individual parameters (id, subject, description, status_id, priority_id, assigned_to_id, due_date). The description doesn't clarify what these fields represent, their formats beyond schema constraints, or relationships between them.

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 ('Update'), target resource ('an existing issue in Lychee Redmine'), and scope ('Partial updates supported'). It distinguishes from 'create_issue' by specifying 'existing issue' and from 'search_issues' by focusing on modification rather than retrieval. However, it doesn't explicitly differentiate from other potential update operations that might exist.

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 implies usage for modifying existing issues ('Update an existing issue') and mentions partial updates as a feature. It doesn't provide explicit guidance on when to use this tool versus alternatives like 'create_issue' for new issues or 'search_issues' for finding issues. No exclusions or prerequisites are mentioned.

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