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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds two non-obvious traits the annotations do not: eventual consistency and the paged/one-cursor-at-a-time constraint. It does not disclose rate limits or the response envelope shape.

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?

A single dense paragraph with the resource and returned fields front-loaded, then ordering, then paging constraints, then the endpoint. Every clause carries information, though the nested parentheses make it slightly harder to scan than it could be.

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?

With no output schema, the description compensates by enumerating the fields present on each conversation (title, type, tags, archived, assignee, participants, last message time) and by explaining the paging cursor behavior. Nothing needed to call it correctly appears to be missing.

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 coverage is 100%, so the baseline is 3, but the description goes beyond it by clarifying that start_from bounds the *ordering* time rather than creation time and that it and pagination_token are mutually exclusive. That is real semantics the schema fields do not convey.

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 and resource (list the organization's conversations) and immediately enumerates the returned fields and the ordering options, making it distinguishable from narrow siblings such as sprucehealth_list_contact_conversations. An agent can tell what it gets without opening the schema.

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?

Gives a concrete use case for start_from ('what changed since…') and an explicit mutual-exclusion rule for start_from vs pagination_token, which is genuine when-to-use guidance. It does not, however, name a sibling alternative (e.g. list_contact_conversations) for the scoped case, so it stops short of full routing guidance.

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