hubspot_search_meetings

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

No annotations are provided, so the description must carry full burden. It explains parameters and defaults but does not disclose any behavioral traits like read-only nature, rate limits, or data freshness. The description is neutral but lacks 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 concise and well-structured: a single-sentence summary followed by a bulleted list of arguments with clear explanations. Every sentence adds value, and it is front-loaded with the core purpose.

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 complexity (6 parameters, no annotations, many siblings), the description covers key aspects: date range, filters, defaults, and pagination. Output schema exists, so return values are not needed. Minor omission: nature of owner ID format, but overall adequate.

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%, so the description compensates well by adding defaults (start_date, end_date, limit), example values for outcome, and explanation of after for pagination. This goes beyond the schema's titles and defaults.

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 the tool's purpose: 'Search HubSpot meetings within a date range, optionally by owner/outcome.' It identifies the specific resource (meetings) and allows filtering, distinguishing it from sibling search tools for companies, contacts, deals, etc.

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 meetings with optional filters and pagination. It provides defaults and examples, but does not explicitly state when not to use it or contrast with alternatives. Still, it gives sufficient context for correct invocation.

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