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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no mention of how `page` behaves (size, defaults, whether results are paged or capped) or how multiple payload conditions are combined, which is the operationally risky part of this tool.

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 with no padding, and the purpose leads. But brevity here reflects under-specification rather than economy — the content that would make it usable was never written.

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?

A read-only filter tool with a nested, order-dependent payload structure, one undescribed parameter, and no output schema, yet the description gives only a one-line restatement. It omits the pagination semantics, the filter-combination logic, and any routing versus sibling list/filter tools — an agent cannot call this correctly on the description alone.

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 only 33%: `page` and the top-level `payload` array are undocumented, and the payload array is precisely the semantically tricky part (an ordered list of conditions joined by query_operator). The description says 'custom filter options and pagination' but supplies no meaning beyond the field names already in 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?

The first sentence is a verbatim restatement of the title, and the second adds only 'custom filter options and pagination' — a vague restatement of the schema rather than a clarified purpose. It names the verb+resource ('filter conversations') but does nothing to separate it from siblings like conversation_list, contact_filter, or list_all_filters.

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?

There is no when-to-use guidance at all: no statement of when to prefer this over conversation_list or contact_filter, and no note that this reads filtered results rather than creating a saved filter (create_a_custom_filter). The agent must infer usage entirely from the name.

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