get_role

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

With no annotations provided, the description bears full responsibility for disclosing behavior. It only states the action (get) and resource, implying a read operation. There is no mention of authorization requirements, error conditions (e.g., role not found), side effects, or response structure. While the presence of an output schema documents return values, the description adds no behavioral context beyond the obvious.

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 sentence of 10 words, front-loading the verb and resource. Every word is necessary and no redundant information is included. It is appropriately sized for a simple retrieval tool.

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, output schema present), the description is largely adequate for an agent to invoke it correctly. It could be improved by clarifying that the role must exist and by explaining what 'CDV' stands for, but these are minor gaps. The existence of an output schema compensates for the lack of return value description.

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 single parameter 'object_id' is described as 'numeric ID' in the description, aligning with the schema's integer type. However, with 0% schema description coverage, the description adds marginal meaning by specifying the ID refers to a role. It does not explain that the ID must correspond to an existing role or provide format/length constraints beyond the integer type.

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 explicitly states 'Get a single CDV role by its numeric ID', which clearly identifies the verb (get), resource (CDV role), and the method (by numeric ID). This distinguishes it from sibling tools like list_roles (which retrieves multiple) and create_role (which creates).

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 such as list_roles, create_role, or delete_role. The description does not mention any prerequisites, limitations, or typical use cases, leaving the agent to infer context from the tool name and siblings.

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