Api pmbok responsibility matrix activities 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 without the description. The description adds no behavioral context of its own – nothing about what object shape is returned, whether related actors/assignments are included, or error behavior for unknown ids.

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 a single line with no wasted words, but this is under-specification rather than conciseness – the line carries zero information beyond the tool name already shown to the agent.

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?

With no output schema, no schema descriptions, and a large, near-identical sibling set, the description must carry the burden of explaining the resource and the return value. It does neither, so an agent has no basis for choosing this over the parallel '..._activities_retrieve' tool.

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 description coverage is 0% for the single required 'id' parameter, so the description is the only place that could clarify whether it is a UUID, integer, or ref_id. It says nothing, leaving the identifier format and lookup key undocumented.

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 identifier 'api_pmbok_responsibility_matrix_activities_object_retrieve' restated verbatim, which is a tautology rather than an explanation. An agent can infer from the name that it fetches a single responsibility-matrix activity, but nothing in the description confirms the resource, and the distinction from the sibling '..._activities_retrieve' is left entirely unstated.

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?

There is no when-to-use guidance, no prerequisite or exclusion, and no mention of the alternative tools for the same resource ('..._activities_retrieve', '..._activities_list', '..._activities_cascade_info_retrieve'). The agent must guess which retrieve variant to invoke.

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