List Project Distribution Groups

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

Annotations already indicate readOnly, non-destructive, idempotent, and open world. Description adds: returns paginated JSON array of Directory records with pagination metadata. It also mentions the endpoint and API version, providing operational context beyond annotations. No contradiction.

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?

Three sentences: purpose, usage guidance, required param and API info. No redundant words. Front-loaded with key action and subject. Well-structured.

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 9 parameters and no output schema, description covers main aspects: purpose, return type (paginated JSON array of Directory records), pagination control, required parameter, and API endpoint. Missing explicit mention of filtering options beyond pagination, but schema handles those. Reasonably 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 description coverage is 100% so baseline is 3. Description mentions page and per_page for pagination and required project_id, but does not add extra meaning for other parameters (e.g., domain_id, ual) beyond what the schema already provides. Adequate but not enhanced.

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?

Description clearly states it returns a list of all Distribution Groups for a project, with specific use cases like paginated overview, finding IDs, and filtering. It explicitly associates the tool with a project, distinguishing it from sibling tools like list_distribution_groups (without project scope) and show_project_distribution_group (single record). Verbal verb+resource combination is precise.

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?

Description advises use for enumeration, pagination, and filtering. It implies context (need project_id) and gives the API endpoint, but does not explicitly state when not to use or name alternative tools for single record lookup. Clear enough for typical usage.

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