Api pmbok responsibility matrices destroy

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that: no statement of what cascade effects deleting a matrix has (activities, actors, assignments), whether deletion is recoverable, or what permissions are required. Since it does not contradict the annotations, it is not a contradiction, but it contributes essentially zero additional 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?

It is short, but shortness here reflects under-specification rather than concision. It is not front-loaded with any meaningful statement and offers nothing beyond the identifier.

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, open-world delete tool with no output schema and an undocumented required parameter, the description must carry the burden of explaining scope and consequences. It provides none of that, so an agent cannot confidently decide to invoke it.

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 required 'id' string parameter carries no description. The description does not identify what the id refers to (matrix PK? ref?) or its format, leaving the only parameter undocumented across both sources.

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 only the raw tool name repeated in snake_case ('api_pmbok_responsibility_matrices_destroy'). It is a restatement of the identifier with no verb+resource phrasing an agent could parse, and it does not distinguish this from sibling matrix tools (create/update/list/retrieve/cycle_cell).

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 indication of when to use this versus alternative matrix operations, no prerequisites, no mention of what the id must reference. The 'destroy' suffix is the only hint, and it duplicates the name rather than guiding behavior.

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