List RFI Default Distribution

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds value by mentioning paginated JSON array output, pagination metadata, and the specific API endpoint, but does not discuss permissions or ordering. No contradiction with annotations.

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, with only a few sentences. It front-loads the purpose and includes necessary details about pagination and required parameters. Every sentence adds value without unnecessary repetition.

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 no output schema, the description adequately explains what the tool returns (paginated JSON array of RFI records with metadata). For a simple list operation, this provides sufficient context for an AI agent to understand the output structure.

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%. The description adds meaningful guidance for page and per_page parameters (control pagination, response includes metadata) beyond the schema descriptions. For project_id, no extra meaning is added beyond specifying it is required, which is already in 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 title and description clearly state the tool returns a list of contacts for the RFI default distribution. The description specifies it is for enumerating RFI records with pagination and filtering, distinguishing it from similar list operations like list_rfis.

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 clear context for when to use the tool (for paginated overview, finding IDs, or filtering), but does not explicitly mention when not to use it or compare to alternatives such as list_rfis or list_default_distribution_members. This is a minor gap.

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