hs_crm_search

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'search', implying read-only, but does not confirm idempotence, permissions, or side effects. No mention of rate limits, pagination, or error behavior. A docs link is given but does not inline key details.

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?

Extremely concise: two sentences plus a link. Front-loaded with 'Escape hatch' for instant context, no wasted words, and every sentence adds value.

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?

Adequate for a search tool given the presence of many siblings, but lacks behavioral transparency and parameter detail. Does not mention result format, pagination, or read-only nature, which are important for correct invocation.

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 description mentions 'custom filter conditions' and 'any object type', but does not elaborate on how to use the parameters (e.g., filter structure, operator semantics, property selection, sorting, limit). Schema descriptions cover 60% of parameters, but the description adds no value beyond them, failing to compensate for the remaining 40%.

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?

Clearly states it performs a structured CRM search against any object type, and explicitly distinguishes from preset tools by labeling itself an 'escape hatch'. This makes its purpose specific and differentiated from siblings.

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?

Directly advises to use when preset tools don't cover the query, providing clear context for tool selection. Lacks explicit exclusion of other scenarios but the guidance is sufficient for an agent.

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