Get Custom Role

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

The annotations already declare readOnlyHint=true, and the description reinforces this by explicitly stating the tool is read-only and that roles, members, teams, and SSO are intentionally not modifiable through MCP. This adds meaningful behavioral context beyond the annotations, though it does not discuss return format or errors.

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 compact, front-loads the core purpose, and every sentence contributes either to understanding the return value, locating the parameter, or clarifying behavioral constraints. No filler or repetition.

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 read operation with a fully documented schema and readOnlyHint annotation, the description provides enough information to invoke the tool correctly: what it returns, where the ID comes from, and the required context. No output schema exists, but the description compensates by listing key return fields.

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 describes roleId as the public ID (GUID) with 100% coverage. The description goes further by explaining where to obtain the ID, which adds practical meaning beyond the raw schema definition.

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 identifies the action ('Get one custom role by ID') and the specific resource, then enumerates exactly what information is returned: permission strings, member count, and last-changed time. This distinguishes it from the sibling list_custom_roles, which retrieves multiple roles.

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 provides explicit guidance on how to obtain the required roleId, pointing to list_custom_roles and a member's customRoleId, and notes the required organization context. It does not explicitly contrast with list_custom_roles, but the ID-sourcing instruction implies the appropriate alternative usage.

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