Get role

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

The annotations already provide readOnlyHint and openWorldHint, covering the safety profile. The description adds no behavioral context beyond the title, such as the effect of the 'with' parameter on the response or the exact return format, so it provides minimal additional transparency.

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 with zero waste, front-loading the essential action and resource. It is appropriately concise and directly to the point.

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 simple GET-by-ID tool, the description is minimal, but the presence of the undocumented 'with' parameter and the lack of an output schema leave significant gaps. The agent is not informed about what data is returned or how 'with' alters the response, making the description insufficiently complete for full autonomous use.

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?

With schema description coverage at 0%, the description carries the burden of explaining parameters. It implicitly identifies 'id' as the role identifier but says nothing about the 'with' parameter, leaving its semantics and possible values unexplained.

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 uses a specific verb 'get', identifies the resource 'role', and includes the qualifier 'by ID'. This clearly distinguishes it from sibling tools like kommo_roles_list, kommo_roles_create, and kommo_roles_update.

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 that this tool is used when you have a specific role ID and need its details. However, it does not explicitly state when to use it instead of alternatives like kommo_roles_list, nor does it mention any exclusions or alternative tools.

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