hubspot_search_contacts

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

The description flags the tool as 'READ-ONLY' and explains pagination via the 'after' cursor parameter. However, since no annotations are provided, the description carries the full burden, and it does not disclose rate limits, authentication needs, or behavior when no results are found.

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 extremely concise, using a bullet-like list for parameters under 'Args:' with no wasted words. The main purpose is front-loaded in the first line. Every sentence is necessary.

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 output schema exists, return values do not need explanation. The description covers input parameters and pagination well, but it could explicitly state that the tool returns a list of contacts matching the filters and specified properties. It is mostly 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?

With 0% schema description coverage, the description adds significant meaning: it explains filters as 'JSON string of HubSpot filter groups array', properties as comma-separated, dates as ISO filters, and pagination via 'after'. This compensates well, though the exact filter format could be more detailed.

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 'Search HubSpot contacts with filters (READ-ONLY)', specifying the verb 'Search' and resource 'HubSpot contacts'. It distinguishes itself from sibling tools that search other entities (e.g., companies, deals).

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 searching contacts with filters but provides no explicit guidance on when to use this tool versus alternatives (e.g., hubspot_get_contact for a single contact). No exclusions or when-not-to-use are mentioned.

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