List question groups

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds valuable behavioral details: it calls the 'list_groups' method and notes that authentication uses the configured service account (so the agent should not provide a session key). This goes beyond what annotations provide.

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 two sentences: one for purpose, one for implementation details. It is front-loaded and every sentence adds value. No waste.

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 that the tool has an output schema (not shown but indicated), the description does not need to describe return values. It covers the purpose, method, and authentication. However, it lacks any mention of pagination or filtering, which might be relevant for a list tool, but given simplicity (3 params, no nested objects), it is mostly complete.

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?

Schema coverage is 100%, so all parameters have descriptions. The description does not add new meaning to parameters beyond the schema. It mentions the required survey_id implicitly, but no extra semantics. Baseline 3 is appropriate.

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 tool lists question groups in a survey, with a specific verb 'List' and resource 'question groups'. The title 'List question groups' matches, and the tool is distinct from sibling tools like 'list_questions' or 'list_quotas'.

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 some context (calls specific method, authentication note) but does not explicitly state when to use this tool vs alternatives. Among many siblings, it would be helpful to clarify, e.g., 'Use this to get all groups; for individual group properties, use get_group_properties.' The usage is implied but not explicit.

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