hubspot_search_contacts

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

The description adds behavioral context by noting that it routes through the domain-agent dispatcher under JWT, tenant, and company scope, which goes beyond the annotations. However, it does not explicitly address the destructiveHint=true annotation, leaving potential side effects unspecified, though the name 'search' implies read-only.

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 concise and well-structured, with a clear action statement, routing context, and parameter definitions. There is no redundant or excessive wording.

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 simplicity of the tool (two optional parameters and no explicit output requirements), the description provides sufficient context for an agent to understand when and how to invoke it, especially alongside the sibling tools listed.

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?

Both parameters are explained beyond their schema types: 'message' is described as a free-text objective and 'inputs' as an optional JSON string for structured inputs. This fully covers their intended use.

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 that the tool runs the 'search_contacts' action on the HubSpot domain agent, naming the specific resource and action. It also explains the routing through the domain-agent dispatcher, making its purpose unambiguous and distinct from other tools.

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 usage context by listing the 'message' and 'inputs' arguments with their semantic meaning, making it clear how to invoke the tool. It does not explicitly mention alternatives, but the specificity of the action and parameters leaves little room for confusion.

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