getRole

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

No annotations are provided, and the description does not disclose any behavioral aspects. The tool likely performs a read operation, but this is not stated. There is no information about side effects, permissions, rate limits, or what gets returned.

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 short (2 words), but this is not conciseness; it's under-specification. It lacks essential information. A concise description would be informative yet brief, but this one is insufficient.

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 the complexity (two parameters, nested object, no output schema), the description is completely inadequate. It provides no context on what the tool returns, how to interpret the output, or any behavioral notes. The context signals show a need for more detail.

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 description does not mention any parameters. The input schema includes pathParams (format and roleId), but the description adds no meaning beyond what the schema provides. With 0% schema description coverage, the description fails entirely to clarify parameter usage.

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 'Show role' is basically a tautology of the tool name 'getRole'. It does not specify what role is shown, nor does it differentiate from sibling tools like 'getRoles' that list roles. The purpose is vague and minimally informative.

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?

No guidance is provided on when to use this tool vs alternatives (e.g., getRoles). There are no mentions of prerequisites, context, or conditions. The description gives no help in selecting the correct tool.

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