Api pmbok responsibility matrix actors create

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

Annotations already disclose readOnly=false, idempotent=false, destructive=false and openWorld=true, so the safety profile is covered structurally. The description adds nothing beyond that — no statement about what gets created, whether the actor is scoped to a matrix, or what permissions are needed for a write operation.

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 short, but this is under-specification rather than conciseness — the single string duplicates structured data and carries zero information payload.

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?

This is a mutation endpoint with an untyped body, no output schema, and no annotations covering semantics. The description supplies none of the missing context an agent would need to call it correctly.

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 one optional 'body' parameter typed as a free-form object with 0% schema description coverage, and the description says nothing about its shape or required fields. With the schema opaque and no compensating text, an agent cannot know what payload 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 a verbatim restatement of the tool name ('api_pmbok_responsibility_matrix_actors_create') with no expansion. An agent can infer 'create an actor in a PMBOK responsibility matrix' only by parsing the identifier itself, and nothing distinguishes it from siblings such as pmbok_responsibility_matrix_actors_batch_action_create or _update.

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 create a matrix actor versus using the batch-action, update, or partial_update siblings, and no mention of prerequisites (e.g. an existing responsibility matrix ID that the actor must attach to). The description offers no context at all.

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