hubspot_search_calls

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. The description only says 'Search call engagements' without mentioning that it supports full-text search, filtering, pagination, or property selection. No details about authentication needs, rate limits, side effects, or return format are given.

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 (one sentence), but it is under-specified rather than efficiently informative. Important details about functionality, parameters, and usage context are omitted, making the conciseness detrimental to tool understanding.

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 tool's complexity (5 parameters, no output schema, no annotations), the description is grossly incomplete. It fails to explain pagination behavior, filter structure, property selection, or response format, leaving the agent with insufficient information to use the tool correctly.

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 description coverage is only 40% (query and filters have descriptions). The tool description does not add any parameter semantics beyond what is already in the schema. For the undocumented parameters (after, limit, properties), no additional context is provided, so the agent must rely solely on parameter names which may be ambiguous.

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 states the verb 'Search' and resource 'call engagements', making the basic purpose clear. However, it does not distinguish from sibling tools like hubspot_list_calls (listing all calls) or hubspot_get_call (getting a specific call), which could cause confusion for an AI agent selecting the appropriate tool.

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?

No guidance is provided on when to use this search tool versus alternatives like hubspot_list_calls or hubspot_get_call. There is no mention of prerequisites, use cases, or circumstances under which this tool is preferred.

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