list_all_addresses

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the confirmation 'Makes no changes' and the HTTP method 'GET'. This is consistent but does not disclose additional behavioral details like pagination behavior or rate limits.

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 extremely concise—three lines including a visual icon, endpoint, and a clear statement of purpose. Every sentence adds value without redundancy. It is front-loaded with key information.

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?

While the description clearly indicates a read-only list operation, it omits details about the response structure, pagination behavior, or how the returned data is shaped. With no output schema, the agent must guess the response format. Given the tool's complexity (4 parameters, nested objects), the description is incomplete.

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?

The input schema has 100% coverage with descriptions for all four parameters (limit, offset, orders, filters). The description does not elaborate on these parameters beyond what the schema provides, so it meets the baseline but adds no extra meaning.

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 'List all addresses' and 'Fetches data. Makes no changes to your ActiveCampaign account.' The title 'List all addresses' and the READ-ONLY badge provide a specific verb and resource, distinguishing it from sibling tools like 'list_all_contacts' or 'list_all_accounts'.

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 provided on when to use this tool versus alternatives. It does not mention exclusions (e.g., 'for filtered addresses use search_*') or contrasting with other listing tools. The user must infer that this is the generic address listing tool.

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