provider_get_role

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered elsewhere. The description contributes nothing beyond that — no note on whether the role is org-scoped, whether a 404 is expected for unknown ids, or what the payload roughly contains.

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?

Very short and front-loaded, but the second line duplicates the annotation title verbatim (GET /cloudapi/1.0.0/roles/{id}) and consumes half the description with redundant text while useful guidance is absent.

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 single-resource read with a fully documented one-parameter schema and safe annotations, this is minimally adequate. However, with no output schema the description could have sketched the returned role shape or identified the id source, and it leaves the agent unable to distinguish this from role-listing siblings.

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 100% with a single required `id` (path) parameter, so the schema already documents the input. The description adds no meaning about the id's format (URN vs. numeric) or where to obtain it. Baseline 3 applies when the schema does the work.

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?

"Get specified role" states a verb and resource, but it essentially restates the tool name and adds no distinguishing information about what kind of role (provider role vs. tenant role) is returned. The only additional content is the raw REST path, which does not help an agent differentiate this from siblings such as provider_query_tenant_roles or provider_query_rights.

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?

No when-to-use guidance at all. There is no mention of when to call this single-role fetch versus provider_query_tenant_roles or provider_query_role_rights, and no statement of prerequisites or expected context.

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