Api pmbok responsibility assignments list

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally and the description does not contradict it. However, the description adds nothing behavioral - no mention of pagination, filtering scope, or what the 'optimized data' injection means for the returned payload. It describes the server's internals rather than observable behavior.

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 short sentence with no filler, but that is because it says almost nothing. The one sentence is spent on an implementation detail rather than front-loading the resource, scope, or filtering behavior an agent needs.

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 10-parameter list endpoint with no output schema, no parameter documentation, and many near-identical sibling list/retrieve tools, the description is completely inadequate. It leaves the agent unable to know what the tool returns or how to use its filters.

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 are 10 parameters (id, role, actor, activity, limit, offset, search, ordering, max_pages, activity__matrix) with 0% schema description coverage, and the description explains none of them. Filtering semantics, the meaning of limit/offset/max_pages, and valid ordering values are entirely undocumented anywhere.

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 text 'Override the list method to inject optimized data into the serializer context' is a developer implementation note, not a statement of what the tool does for a caller. It mentions 'list' and, indirectly through the name, responsibility assignments, but never says it returns a collection of PMBOK responsibility assignments or what those entities represent. The purpose is only inferable from the tool name, not the description.

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 guidance on when to call this versus the sibling retrieve/object_retrieve/cascade_info_retrieve endpoints for the same resource. The sentence describes an internal override, which gives an agent no usage context or exclusions.

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