Delete Action Plan Reference

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

Annotations already declare destructiveHint=true and readOnlyHint=false, indicating a destructive operation. Description adds emphasis with 'This cannot be undone' and 'Permanently removes', but does not disclose additional behaviors (e.g., cascading deletes, authorization needs). No contradiction with annotations.

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?

Description is somewhat repetitive, stating permanent deletion twice ('This cannot be undone' and 'This action cannot be undone'). Includes useful API context but could be more concise. Front-loads the action but repetition hurts efficiency.

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 simple delete tool with two parameters and annotations covering destructiveness, the description is adequate. However, it fails to clarify that the tool deletes a reference, not the action plan itself, which could lead to misuse. No output schema, so return info not required.

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?

Input schema has 100% coverage with descriptions that already state the parameters are URL path identifiers. The description repeats 'Required parameters: project_id, id' and adds the endpoint URL, but adds no new semantic meaning beyond the schema.

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?

Tool name and description indicate deletion of an action plan reference, but description repeatedly says 'specified Action Plans' which could confuse with delete_action_plan. The verb and resource are mostly clear but the inconsistency with the tool name (reference vs plan) reduces clarity.

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 guidance on when to use this tool versus alternatives like delete_action_plan or bulk_delete_action_plan_references. The description only lists required parameters and API endpoint, failing to help an agent decide among sibling tools.

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