Api ebios rm stakeholders 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 known; the description contributes nothing on top of that. It does not state what happens to dependent records (e.g. stakeholders referenced by strategic scenarios), whether deletion is soft or hard, or what permissions are required for a destructive operation. 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?

It is only one token, so there is no verbosity, but that brevity comes from under-specification rather than efficiency. Nothing is front-loaded because there is nothing to front-load.

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-idempotent-looking endpoint on a specific domain object, the description supplies none of the context an agent needs: identifier format, cascade side effects, or confirmation requirements. No output schema exists to offload that burden elsewhere.

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 parameter 'id' is a bare string with no format hint. The description does not say whether this is a numeric primary key, a UUID, or a ref_id, leaving the one thing an agent must supply unexplained.

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 name repeated ('api_ebios_rm_stakeholders_destroy'), which is a tautology rather than an explanation. An agent can infer that it deletes an EBIOS RM stakeholder from the 'destroy' suffix, but the text itself adds no verb, resource, or scope statement beyond what the name already encodes.

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 usage guidance at all: no when-to-use, no when-not-to-use, and no pointer to alternatives such as the sibling stakeholders_partial_update or stakeholders_retrieve. The agent must guess entirely from the name.

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