redmine_get_issue_context

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

No annotations are provided, so the description carries the full burden. It discloses the return format (JSON with specific fields), but it does not explicitly state that this is a read-only operation, how errors are handled (e.g., if the task key is invalid or the issue does not exist), or any authentication/rate-limit considerations. The description adds some value by listing the returned fields, but it lacks depth in behavioral disclosure.

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, focused sentence that conveys the purpose, the input example, and the output structure without any filler. Every word earns its place, making it highly concise and efficiently structured.

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 tool with one parameter and no output schema, the description covers the essential aspects: what the tool does, how to use it, and what it returns. It does not discuss error cases or side effects, but for a straightforward getter, the description is sufficiently complete. The lack of annotations is compensated by the clear mention of returned JSON fields.

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 schema already provides a clear description for taskKey, including a pattern and example. The description adds a slightly different example but does not provide additional semantic information beyond what the schema contains. Since schema coverage is 100%, the baseline of 3 is appropriate; the description does not compensate for any gaps because there are none.

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 tool's function: "Get Redmine issue by task key" with a concrete example (PROJECT-123) and explicitly lists the return fields (id/key/tracker/subject/description/comments). It is specific, uses a clear verb+resource structure, and leaves no ambiguity about what it does.

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: it tells you it fetches an issue by its task key, which is sufficient in the absence of sibling tools. However, it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. Since there are no sibling tools provided, this vagueness is not critical, but the lack of explicit context prevents a higher score.

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