Api pmbok responsibility roles object retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no note on permissions, 404 behavior on unknown id, or what the returned role object 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?

It is technically short, but the brevity comes from under-specification rather than efficiency — there is no front-loaded statement of action or result, just a snake_case identifier that duplicates the tool name.

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 read-only single-object retrieve with no output schema, the description should at minimum say what entity is returned and what the id refers to. None of that is present, so an agent cannot call it confidently against the many similarly named pmbok 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?

There is a single required parameter 'id' with 0% schema description coverage, and the description does not say whose id it is (role id vs. matrix id vs. project id) or its format. With no compensating text, the agent must guess the identifier's scope.

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 is the operation ID repeated verbatim ('api_pmbok_responsibility_roles_object_retrieve'), so it only restates the name. An agent can infer a single-object retrieve on a PMBOK responsibility role, but nothing states what the resource is or what distinguishes it from the sibling *_retrieve, *_list, or *_cascade_info_retrieve tools.

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, no prerequisites, no exclusions. The 'object_retrieve' suffix weakly implies fetching one record by id versus the sibling list operation, but that is inference from the name, not stated guidance.

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