Api pmbok responsibility matrix actors update

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

Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether this replaces the whole actor record (vs. partial update), what fields are mutable, or what happens to omitted fields.

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?

The text is short but only because it is under-specified rather than economical — it is a bare identifier with zero information content. Nothing is front-loaded because there is nothing to front-load.

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 mutation tool with two parameters, no output schema, no parameter documentation and four behavioral annotations, the description carries none of the burden it needs to. An agent cannot safely construct a call from this definition.

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% and the description offers no parameter information at all. The required 'id' and the opaque 'body' parameter (anyOf object with additionalProperties=true, default null) are completely undocumented, so an agent has no way to know what to send.

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 literally the tool's operation id ("api_pmbok_responsibility_matrix_actors_update"), which restates the name and title without adding any explanation. An agent can parse 'update' and 'actors' from the identifier, but nothing states what a responsibility-matrix actor is or what updating one entails.

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 is given, and the sibling list contains near-identical routes (actors_create, actors_partial_update, actors_destroy, actors_update). The critical distinction between this full update and actors_partial_update is left entirely to inference.

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