Api chat questionnaire questions 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, and the description adds no behavioral context on top of them — nothing about cascade effects, whether answers tied to the question are removed, or permission requirements. For a destructive operation, this is a serious omission.

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 short, but brevity here comes from under-specification rather than economy; it conveys zero information beyond the tool name and has no front-loaded statement of purpose.

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?

A destructive, open-world delete endpoint with no output schema and no described parameter needs far more explanation than a name echo. Nothing an agent needs in order to call it safely — what gets removed, irreversibility, cascade behavior — is present.

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 'id' parameter has 0% schema description coverage and the description says nothing about it. It is not stated whether 'id' is the questionnaire question UUID or a related run/question identifier, leaving the caller to guess.

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_chat_questionnaire_questions_destroy'), which is the definition of tautology. An agent can only infer the resource and action by parsing the machine-generated name, not from any prose description.

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, or which sibling to prefer. It does not point to alternatives like ciso_assistant_api_chat_questionnaire_questions_list or _partial_update, nor does it mention prerequisites for deleting a questionnaire question.

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