search_contact_in_funnels

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

Annotations already indicate readOnlyHint=true, so the description adds that it returns funnel and stage. However, it does not disclose behavior for edge cases (e.g., no matching contact) or the response format beyond the stated return. The description adds some value but not extensive depth.

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 long, directly stating the action and result. It is front-loaded with the key information and contains no unnecessary details.

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 the simple search functionality, annotations, and sibling tools, the description covers the main purpose and return value. It lacks explicit mention of what happens if no contact is found or whether multiple results can be returned, but for a search tool this is fairly complete.

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 0% (no parameter descriptions in schema). The description mentions the two parameters and that search can be by either phone or uuid, but it does not provide format, constraints, or which parameter is preferred. It adds minimal semantic value beyond the parameter names.

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 specifies the verb 'search', the resource 'contact within funnels', and the search criteria (phone number or contact_uuid). It also states the return value (funnel and stage), distinguishing it from siblings like get_contact or list_funnels.

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 the tool is used to find a contact's funnel and stage by phone or uuid, but it does not explicitly mention when to use it versus alternatives (e.g., get_contact for contact details, move_contact_to_funnel_stage for moving) or any prerequisites or exclusion cases.

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