List survey groups

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

Specifies backend method and auth details, complementing annotations (readOnlyHint, idempotentHint). Does not contradict annotations, though adds implementation detail beyond them.

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 sentences, front-loaded with purpose, no filler. Every sentence is necessary and informative.

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?

Covers purpose, auth, and backend method. Output schema exists, so return format is covered. Slight gap on pagination or limits, but overall sufficient for a simple list tool.

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?

Adds value beyond schema by explaining auth handling and that no session key is needed, which is relevant to parameter usage (username is optional). Schema coverage is 100%.

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?

Clearly states 'List survey groups visible to a user' with verb 'list' and resource 'survey groups', distinguishing it from siblings like limesurvey_list_surveys and limesurvey_list_groups.

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?

Provides authentication context: 'use configured service account; do not provide a session key', but lacks explicit comparison to alternative listing tools like limesurvey_list_groups.

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