Api crq quantitative risk scenarios create

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

Annotations already disclose readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the mutation/safety profile is partially covered by structured data. However, the description supplies nothing beyond those annotations – no mention of required parent context (e.g. which quantitative risk study a scenario belongs to), permissions, validation behavior, or whether re-invocation creates duplicates (which matters given idempotentHint=false).

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?

The text is a single token with no wasted words, but this is under-specification rather than conciseness. There is no front-loaded statement of purpose, scope, or payload expectations.

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 mutating, open-world create endpoint with an opaque request body, no output schema, and dozens of closely named CRQ siblings, the description does nothing to make the tool safely invocable. All of the substantive information an agent would need is absent.

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 schema exposes exactly one parameter, 'body', typed only as an untyped object-or-null with schema description coverage at 0%. The description provides no field-level meaning for that body, so an agent has no idea which scenario attributes must be supplied, which makes the opaque payload a serious usability gap.

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's own identifier repeated back verbatim, so it is a tautology that restates the name rather than explaining the operation. Only the name itself conveys that this creates quantitative risk scenarios under the CRQ module; the prose adds no verb+resource explanation and does nothing to distinguish it from sibling tools such as crq_quantitative_risk_scenarios_batch_action_create or quantitative_risk_hypotheses_create.

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 whatsoever on when to use this tool, when not to, prerequisites, or which sibling tool is the alternative. An agent must infer from the name alone whether to create a scenario, use batch_action_create, or target hypotheses instead.

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