get_ranger_role

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

No annotations provided; description merely states retrieval, omitting details like error handling, behavior when both parameters are provided or none, or response structure. The burden falls entirely on the description.

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?

Single sentence, front-loaded with essential information. No unnecessary words.

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 0% schema coverage, no annotations, and many sibling tools, the description lacks detail on return value, parameter interaction, and use cases. Output schema exists but description does not leverage it.

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?

Schema coverage is 0%, so description adds meaning by indicating either id or name can be used. However, it does not clarify behavior when both or neither are provided, which is needed.

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?

Description clearly states the verb 'Get', resource 'role', and criteria 'by id or name'. It distinguishes from sibling tools like list_ranger_roles and create_ranger_role by specifying identification of a single role.

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?

Implies usage for retrieving a single role by id or name but provides no explicit guidance on when to prefer this over list_ranger_roles or other retrieval tools.

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