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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a genuine operational constraint — "requires read scope" — which is real value beyond the annotations, but it says nothing about ordering, pagination behavior, or result 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?

Two short sentences, front-loaded with purpose and followed by the auth requirement; nothing is redundant or padded. It is perhaps too terse for the tool's scope, but that is a completeness issue rather than a conciseness one.

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?

This is a simple read-only list tool with full schema coverage and annotations, so the burden is low and the auth note plus purpose statement largely suffice. What is missing is disambiguation from the many other list_* conversation/chat tools, which an agent would need in order to choose correctly.

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%, with each of the four parameters (page, page_size, status, campaign_id) documented including defaults, bounds, and the status enum. The description only repeats "optional filtering" and adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and resource ("list conversations") plus a note that filtering is optional, so the agent knows exactly what the tool returns at a high level. It does not distinguish itself from siblings such as list_contact_conversations or list_campaign_chats, leaving scope ambiguity unaddressed.

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?

Usage is only implied: "optional filtering" signals a read-and-browse tool with no required parameters, which the schema confirms. There is no explicit when-to-use guidance and no statement about which sibling to pick for contact- or campaign-scoped conversation listings.

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