get_role

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states 'Get', implying a read operation, but fails to mention any authentication needs, rate limits, prerequisites (e.g., role must exist), or whether the request is idempotent. For a retrieval tool, this is a significant gap.

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 concise sentence that is front-loaded. However, it is overly brief and omits potentially useful context (e.g., what is returned). It earns its place but could be slightly expanded without losing conciseness.

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 tool's simplicity (one parameter, no output schema, no annotations) and the large set of sibling tools, the description is minimal. It lacks details on the return value, error conditions, or typical use cases, making it insufficient for confident invocation 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?

The sole parameter 'id' is already described in the input schema as 'Path parameter: id'. The description adds no additional meaning or format details, such as expected format or constraints. With 100% schema coverage, the baseline is 3, and the description does not improve upon it.

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 'Get role instance by id.' clearly states the action (get) and resource (role instance) with a required identifier. It is specific enough to distinguish from many sibling tools that also start with 'get_', though it could elaborate on what a role instance represents.

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 versus alternatives like list_roles, create_role, update_role, set_role_permissions, etc. The agent must infer based on the name alone, which is insufficient for correct selection.

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