Api ebios rm elementary actions destroy

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false; the description adds nothing beyond them — no statement of what is removed, whether cascade deletion or dependency effects occur, or what permissions are needed. No contradiction, but zero added value.

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 one token long, but this is under-specification rather than conciseness; there is no front-loaded purpose statement or any structure to speak of.

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, non-read-only operation with an undocumented parameter and no output schema, the description supplies none of the information an agent needs before invoking 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?

The single required parameter 'id' has 0% schema description coverage, and the description says nothing about what the ID identifies (an elementary action record) or its format. With only one undocumented parameter, the description had a small job and did not do it.

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 the tool's own identifier repeated verbatim: 'api_ebios_rm_elementary_actions_destroy'. It is a tautology that restates the name and title rather than stating in prose that it deletes an EBIOS RM elementary action.

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 call this versus the many sibling destroy tools (attack_paths_destroy, kill_chains_destroy, feared_events_destroy, etc.), no prerequisites, and no warning about what deletion entails.

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