Api pmbok responsibility matrix actors destroy

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is carried entirely by structured fields. The description adds nothing about what gets destroyed, whether the delete cascades to responsibility assignments, or what permissions are required. It does not contradict the annotations, but contributes zero behavioral context.

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?

There is nothing to trim, but the single token is under-specification rather than conciseness. It provides no front-loaded statement of effect or scope.

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 destructive mutation with no output schema, no annotations beyond hints, and 0% parameter documentation, the description should at minimum state what is deleted and any side effects. It supplies none of this, leaving the agent unable to call it safely.

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 single parameter 'id' is an untyped-meaning string; the description does not clarify whether it is the actor id, the matrix id, or a composite reference. Baseline 4 for zero params does not apply here, and a destroy operation's id semantics are exactly where confusion is costly.

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 identifier restated, so it merely parrots the name and title. The verb 'destroy' and resource 'pmbok responsibility matrix actors' are inferable from the name alone, not from any explanatory text. It does not distinguish this from sibling destroy tools such as responsibility_matrix_activities_destroy or responsibility_matrices_destroy.

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 use this tool, when not to, or which alternative to pick. An agent cannot tell from the description whether deleting an actor is safe, whether it cascades to assignments, or whether a partial_update alternative exists.

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