search_thumbtack

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

The description states the tool returns ratings, reviews, pricing, and hire counts, providing some behavioral insight. However, it does not disclose any side effects, authorization needs, or pagination behavior. Since annotations are absent, more detail would be beneficial.

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 concise sentences front-load the main action and return value, with no wasted words. Every sentence adds useful 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 simple search tool with three parameters and no output schema, the description adequately covers purpose and return data. It lacks details on sorting or default behavior, but is sufficient for agent use.

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 descriptions cover all three parameters (query, location, limit) with examples. The description adds value by listing categories and specifying return fields, which enhances understanding beyond 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 clearly states the tool searches local service professionals from Thumbtack, lists specific categories, and mentions return fields. It uniquely identifies the tool from siblings like search_houzz or search_imdb.

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 usage for Thumbtack service searches and lists categories, but does not explicitly state when to use vs. alternatives or when not to use. However, the context of sibling tools makes the domain clear.

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