list_email_routing_addresses

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it discloses almost nothing: no pagination behavior, no mention that results are account-scoped, no detail on what fields are returned for each address, and no clarification of what 'verified' means in this context. The word 'verified' adds a small behavioral trait, but the description fails to convey the operational behavior of a list endpoint beyond its name.

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 a single five-word phrase with zero waste and the essential information (List + what is listed) front-loaded. It is efficient, though terse to the point of minimalism — slightly more behavioral context would be warranted for this size without harming conciseness.

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?

For a low-complexity single-parameter list operation, the description covers the core purpose adequately. However, with no annotations and no output schema, an agent is left without information about what the response contains (e.g., address and verification status fields), pagination, or why 'verified' is significant. It is minimally viable but has clear gaps.

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% — account_id is documented in the schema as 'The account ID', so the baseline is 3. The description adds no parameter-level meaning beyond the schema, but for a single trivially-named parameter this is an acceptable baseline; there is no gap the description needs to compensate for.

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 uses a specific verb ('List') and a specific resource ('verified destination email addresses'), making the operation unambiguous. The 'verified' qualifier adds useful scoping and helps distinguish this from the related email routing siblings (get_email_routing_settings, list_email_routing_rules). It doesn't explicitly name a sibling for differentiation, but the resource is precise enough that an agent can infer the right selection.

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?

No guidance is given on when to use this tool versus alternatives. There is no mention that this is for Cloudflare Email Routing destination addresses, no context distinguishing it from list_email_routing_rules or get_email_routing_settings, and no exclusions or prerequisites stated. The agent must rely entirely on the tool name for selection context.

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