redmine_get_role

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 states the tool is read-only and returns role with permissions, but it does not disclose error behavior, authentication requirements, or rate limits. For a simple fetch, it is adequate but not comprehensive.

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?

Two concise sentences: the first defines the action and output, the second declares read-only. No unnecessary words, information is front-loaded. Every sentence adds value.

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 fetch tool with an output schema (not shown), the description adequately covers the main purpose and output. It does not cover error scenarios or prerequisites, but given the low complexity, it is nearly complete.

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 has one parameter (role_id) with 0% description coverage. The description mentions 'by id' but does not explicitly describe the parameter or add constraints beyond the schema. Since the parameter is simple and self-evident from the tool name and description, the added value is marginal.

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 'Fetch a role by id, including its permissions list.' It specifies the action (fetch), the resource (role), and the output (permissions list). It is distinct from sibling tools like redmine_list_roles by focusing on a single role by ID.

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?

While the description indicates it is read-only and fetches a single role, it does not provide explicit guidance on when to use this tool versus alternatives like redmine_list_roles to list all roles. 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.