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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered. The description adds the useful fact that posts/messages are included in the response, but says nothing about pagination behavior or the department-defaulting when group_uuid is omitted (that lives only in the schema). Modest added value over 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?

One tight sentence, front-loaded with the action and resource. The trailing raw endpoint fragment ('GET /api/conversations.json?phone_number=…') is the weakest part since it restates structured information, but it is short and does not bloat the definition.

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 lookup with no output schema, the description names the retrieval key, the resource, and that messages are returned alongside the conversation. Pagination and department-default behavior are covered by the schema. Only the absence of an explicit alternative-tool route keeps it from being fully complete.

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% – all six parameters (page, page_size, before/after_uuid, group_uuid, phone_number) are documented in the schema with defaults, ranges, and cross-references. The description only gestures at the phone_number and department concept, adding no syntax or semantics beyond the schema. Baseline 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?

States a specific verb ('Retrieve') and resource ('the conversation with a phone number... and its posts'), plus the lookup key. An agent can tell it fetches a conversation by phone rather than by UUID. It does not explicitly name the sibling textline_get_conversation as the alternate lookup path, so it falls short of the 5 bar.

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: 'if you have a phone number, this gets that conversation and its messages.' There is no explicit when-to-use vs. textline_get_conversation or textline_get_customer_by_phone, and no stated prerequisites (e.g., whether the contact must already exist).

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