roles_get_role_settings

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

The description mentions caching for 15 minutes, which is a behavioral trait. With no annotations, it misses other aspects like error handling or read-only nature.

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 structured with sections and front-loaded. It is concise but the workflow tips and use cases could be slightly more streamlined.

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 no output schema, the description minimally explains the return value ('settings configured'). It mentions visibility and permission settings but lacks details on return structure.

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 'id' is already well-described in the schema. The description provides an example use case but does not add significant meaning beyond the schema.

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 clearly states 'Get role settings' and explains it returns all settings for a specific role. It distinguishes from siblings like roles_get_role_assignments, as it focuses specifically on settings.

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 includes workflow tips and common use cases, providing context for when to use. However, it does not explicitly differentiate from sibling tools or mention when not to use.

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