thumbtack_get_pro

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

Annotations already declare readOnlyHint: true, and the description's 'Read' verb is consistent. The description adds valuable behavioral context by listing what the tool retrieves (profile details, credentials, section inventory), which goes beyond the structured annotation and clarifies the tool's output scope.

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: the first states the purpose and contents, the second specifies the parameter source. It is front-loaded with the core action and all information is relevant, with no redundancy or filler.

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?

Given there is no output schema, the description lists the main returned elements, which gives a good sense of the result. It doesn't explain potential error conditions or what 'section inventory' means, but it is reasonably complete for a read-only tool with a well-defined input source.

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?

The schema already covers the single 'url' parameter fully with a description. The description adds semantic value by specifying that the URL should come from thumbtack_search_pros, which is not in the schema. This helps the agent understand the expected provenance of the parameter.

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 action ('Read') and the resource ('a Thumbtack pro's profile'), and enumerates specific content (name, description, location, rating, credentials, section inventory). It distinguishes itself from sibling tools like thumbtack_get_pro_reviews and thumbtack_search_pros by focusing on the full profile.

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 provides clear context by specifying the input source ('Takes a profile URL from thumbtack_search_pros'), which guides when to use this tool after a search. It doesn't explicitly mention alternatives or exclusions, but the usage context is strong enough for an agent to understand its role.

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