Api crq quantitative risk scenarios 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, so the safety profile is communicated by structured data rather than prose. The description contributes zero additional context — nothing about whether deletion cascades to dependent scenarios, whether it is soft or hard delete, or what authorization is required — so it neither contradicts nor enriches the 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 technically short, but the brevity reflects under-specification rather than efficiency: the single line is the tool name echoed back and carries no front-loadable information. There is nothing to trim because there is nothing there.

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 mutation tool with a required identifier and no output schema, the description should convey at minimum what is deleted and by what key. It conveys neither, leaving the agent to rely entirely on the annotations and a bare schema.

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, so the schema provides no semantics, and the description supplies none either. It does not state whether the id is the scenario UUID, a ref_id, or an integer, which is a real ambiguity here given that sibling endpoints expose default_ref_id and ref_id concepts.

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 a verbatim restatement of the tool name ('api_crq_quantitative_risk_scenarios_destroy'), which is the textbook definition of a tautological purpose statement. An agent can only infer 'delete a CRQ quantitative risk scenario' by parsing the identifier itself; the prose adds nothing and does not distinguish it from siblings like ciso_assistant_api_crq_quantitative_risk_studies_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 when-to-use guidance, no mention of prerequisites (e.g. cascading effects on hypotheses or simulations), and no reference to alternatives such as partial_update if the intent was actually modification. Nothing helps an agent decide between destroy and update.

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