Api pmbok responsibility roles retrieve

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

It does add context beyond annotations by disclosing that fields are masked for unauthorized users — a real data-visibility trait that readOnly/idempotent hints don't cover. However, it doesn't say what gets masked, what the caller needs in order to see full fields, or what happens when the id doesn't exist. Useful but thin.

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?

One short, front-loaded sentence with no filler. Its brevity is efficient even though the content is sparse — no redundancy or buried information.

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-object retrieval tool with no output schema, the description should say what object is returned and how the id identifies it. Neither is present, leaving the agent to guess the resource from the tool name alone.

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 0% for the single required 'id' parameter, and the description says nothing about it — not its type, format, or whether it accepts a UUID, ref_id, or slug. The parameter is entirely undocumented in both schema and description.

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 says only that it returns 'a single object', which without the tool name is meaningless; the resource (a PMBOK responsibility role) is conveyed only by the name, not the text. An agent can infer 'retrieve one' but the description never names the resource being fetched.

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 and no differentiation from the many similar siblings (responsibility_roles_list, _object_retrieve, _cascade_info_retrieve, _taxonomy_retrieve). The agent gets no signal for choosing 'retrieve' over 'object_retrieve' or the list variant.

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