kaiten_get_role

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

With no annotations, the description carries the full burden. 'Get' clearly signals a non-mutating lookup, but it does not disclose response format, error behavior, or access requirements. This is adequate for a simple read but not rich.

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 with zero wasted words. Every part adds meaning: the verb, resource, and retrieval method.

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 trivial get-by-ID operation with a fully documented schema, this is minimally viable. The lack of annotations, output schema, and any mention of alternatives leaves minor gaps in an agent's ability to decide when to use 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?

The schema already fully documents role_id as a UUID string with 100% coverage. The description adds no new parameter semantics beyond rephrasing 'by ID', so the baseline of 3 applies.

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 states a specific verb ('Get'), a concrete resource ('role'), and the retrieval key ('by ID'). It clearly distinguishes this from sibling tools like kaiten_list_roles and other get_* operations.

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 'by ID' qualifier implies the tool is for fetching a single role when a role_id is already known, which provides some usage context. However, it does not explicitly mention when to prefer this over kaiten_list_roles or any exclusions.

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