List profile contacts

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

Annotations already mark readOnlyHint=true and destructiveHint=false; the description adds that the result is paginated, that meta.total counts filter-matching contacts, and that calling without filters yields the profile's total contact count. 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 front-load the core action, then add filter options and response semantics. Every sentence earns its place and there is no filler.

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 read-only list endpoint, the description plus a fully described schema is largely sufficient: pagination, filtering, and the meaning of meta.total are covered. It doesn't spell out the response list field or pagination defaults, but with no output schema those are minor gaps for tool selection and invocation.

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?

All 6 parameters already have schema descriptions (100% coverage), so the baseline is 3. The description paraphrases tag_uuid, subscription_status, and search as filter options but adds no syntax, defaults, or parameter behavior beyond 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?

States a specific operation ('Get a paginated list'), resource ('contacts belonging to a profile'), and available filters. This clearly distinguishes it from broader contact-list siblings like reach_listContactsV1 and segment-scoped listers without relying on the title alone.

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 profile-scoping phrase gives clear when-to-use context, and the filter sentence explains how to adjust for status, tag, or email. It stops short of explicitly naming alternatives or saying when not to use them, so it doesn't reach 5.

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