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

Annotations already cover safety (readOnlyHint true, destructiveHint false, openWorldHint true). The description adds real behavioral context beyond them: deterministic ordering, that sent estimates are interleaved in the thread, that it is scoped to a single conversation, and an auth requirement (Cotlet API key with app access). It does not mention pagination behavior.

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?

It is front-loaded and reasonably short, but 'oldest first' is stated twice and 'one conversation' / 'estimates you sent' are each repeated, so several clauses restate earlier material rather than adding new information.

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 two-parameter tool with no output schema, the description covers what is returned (ordered messages plus sent estimates), how to read them, and the auth prerequisite. Only pagination/default-limit behavior and return shape details are left unstated, which is minor here.

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%, so baseline is 3. The description only indirectly references lead_id ('conversation with the customer on a lead') and adds nothing about the limit parameter, so it does not improve on 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 description states a specific verb and resource: it returns the messages of one conversation on a lead. It also specifies ordering (oldest first) and scope (one conversation), which lets an agent separate it from write siblings like thumbtack_send_message or thumbtack_reply_to_lead without opening either 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?

It gives clear context for use: read the thread before 'answering or pricing,' which ties the tool to the reply and estimate workflows. It does not explicitly name alternative tools or state when not to use it, 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.