thumbtack_resolve_service

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

The description adds behavioral context beyond the readOnlyHint: it explains that the tool asks Thumbtack and that canonicalisation happens via redirect, with a concrete example. It does not discuss rate limits or error cases, but the core behavior is well disclosed.

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?

The description is two sentences, front-loaded with the action, and every phrase adds value. The example is compact and immediately illustrative.

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 minimal tool with two parameters, a read-only annotation, and no output schema, the description fully explains what it does and when to use it. No additional behavioral or context information is necessary.

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% since both parameters have descriptions, but the tool description adds an example ('plumbing' -> 'plumbers') that clarifies the service parameter intent. It also reinforces that zip does not affect the resolved slug, matching the schema description.

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 uses a specific verb-resource pair: 'Resolve a loose service name to the canonical Thumbtack slug.' It clearly differentiates from siblings like search/get by focusing on slug resolution rather than actor search or profile data.

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 explicitly states when to use the tool: 'Use before assuming a slug is right.' This gives a clear directive for appropriate invocation and implies that it should precede other slug-dependent operations.

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