Api chat questionnaire questions cascade info retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds nothing beyond that: it does not explain what the cascade preview computes, whether it is a dry-run of deletions, or what the response looks like.

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?

Two words and a colon are technically concise but the content is under-specified rather than efficient; nothing is front-loaded because nothing substantive is stated.

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 read-only retrieval tool taking an id and returning no documented output schema, the description should at minimum say what is returned and what the id identifies. Neither is present, leaving the agent unable to invoke the tool correctly.

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 it. It is unclear whether the id refers to a questionnaire run, a question, or another entity, so the description fails to compensate for the schema 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?

"Cascade preview:" is a fragment that roughly restates the title/endpoint name rather than stating what the tool does. It hints at a preview of cascade-related data but never says which resource (questionnaire questions) or what a "cascade preview" contains, so an agent cannot distinguish it from the many other *_cascade_info_retrieve siblings.

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 use this tool versus ciso_assistant_api_chat_questionnaire_questions_retrieve, _object_retrieve, or any of the dozens of other cascade_info_retrieve tools. No prerequisites, no exclusions, no context.

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