List surveys

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

Beyond what annotations already indicate (readOnly, idempotent, non-destructive), the description adds valuable context such as the specific RC method used and authentication details (service account, no session key).

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 concise at three sentences, front-loaded with the core purpose, and contains no wasteful or redundant content.

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?

Given the presence of an output schema and detailed annotations, the description provides sufficient context for agent decision-making, though it omits mention of return format.

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 covers all three parameters with descriptions, and the description mentions optional filtering by survey group, aligning with the schema but not adding new semantics beyond it.

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 clearly states the verb 'list' and the resource 'surveys', and specifies optional filtering by survey group, which distinguishes it from sibling tools like limesurvey_list_groups and limesurvey_list_questions.

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 provides authentication guidance and references the underlying RC method, but does not explicitly state when to use this tool versus alternatives like limesurvey_find_surveys.

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