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

Beyond the annotations (which already declare this a safe read), the description discloses substantial behavior: the cost is only charged if you reach out and the customer responds, and an Opportunity closes after 48 hours, five pro responses, or customer cancellation, with closes_at defined as the 48-hour mark. This billing and expiry context is exactly the kind of trait annotations cannot express.

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?

Front-loaded with the verb, but the cost concept is stated three times in close succession ("cost shown upfront," "cost Thumbtack shows before you reach out," "charges that cost only if"), which is redundant. The closing-rules sentence earns its place; the repeated cost phrasing does not.

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 list tool with no output schema and full schema coverage, the description supplies the important missing context: pricing mechanics, expiry rules, and the Cotlet API key requirement. Only token/pagination behavior is left implicit, which the cursor param largely covers.

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% (limit, cursor, service are all documented in the schema), so the baseline is 3. The description adds no parameter-level detail beyond the schema, though it does surface the return field closes_at.

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 ("Lists") and resource ("Opportunities") and immediately defines what an Opportunity is — one you can quote, with cost shown and a closing time. This lets an agent distinguish it from siblings like thumbtack_list_leads and thumbtack_get_lead without opening a 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?

The description implies when this is relevant (browsing quotable opportunities with upfront cost), but it never explicitly contrasts itself with thumbtack_list_leads, thumbtack_get_lead, or thumbtack_reach_out_to_opportunity, nor states when not to use it. Usage must be inferred from context rather than directed.

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