acedatacloud_list_surveys

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

No annotations are provided, so the description must carry the transparency burden. 'List' implies a read-only operation and 'active' plus 'available to the caller' narrows the behavior, but the description does not explicitly state that it is non-mutating or disclose effects like pagination, permissions, or rate limits.

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 description is a single, efficient sentence that is front-loaded with the verb and resource. Every word contributes meaning, with no filler or vague terminology.

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?

This is a low-complexity, zero-parameter list tool with an output schema available, so the description does not need to enumerate return fields. The phrase 'available to the caller' adds useful scoping, though it could still mention whether inactive or draft templates are ever visible.

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 tool accepts zero parameters and schema description coverage is 100%, so the description does not need to explain parameter details. The baseline for no-parameter tools is 4, and nothing in the description conflicts with the schema.

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 uses a specific verb ('List') and clearly identifies the resource ('active survey templates available to the caller'). It also distinguishes this tool from related sibling tools like get_survey and submit_survey by framing it as a list-oriented, template-scoped operation.

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?

The description implies the appropriate use case—listing active survey templates before selecting one—but it does not explicitly say when to use this tool versus get_survey, get_survey_response, or submit_survey. No exclusions or alternatives are named, leaving the guidance mostly implicit.

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