get_role

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

With no annotations, the description must carry the behavioral burden. 'Return' signals a read-style lookup and the description discloses the returned entities: role file, stanza metadata/sizes, and projects. However, it does not address not-found behavior, permissions, or potential side effects, though the get-oriented wording implies none.

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, front-loaded sentence that immediately states the action and the returned data. It contains no filler and each phrase adds distinct information about the tool's output.

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 single-parameter retrieval tool with an available output schema, the description conveys the essential scope of the result set: role file, stanza metadata/sizes, and projects. It lacks explicit routing guidance versus sibling tools, but the low parameter complexity and output schema reduce the need for further 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 schema has 0% description coverage for role_id, and the description does not explain what role_id should be or how to format it. 'One role file' weakly maps role_id to a role, but the description does not compensate for the missing schema documentation.

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 names a specific action, 'Return', and a precise resource: one role file along with member stanza metadata and sizes and including projects. This distinguishes it from siblings like list_roles, get_stanza, and get_project, which either list many items or return different resource types.

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 this is for retrieving a single role's full aggregated details, but it does not explicitly state when to prefer it over list_roles, get_stanza, or get_project. The usage context is inferrable from 'one role file' and the role_id parameter, but no direct alternatives or exclusions are mentioned.

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