search_deals

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

No annotations are provided, so the description must carry the full burden. The verb 'search' implies a read operation, but it does not explicitly state side effects, authentication needs, rate limits, or search semantics (e.g., case sensitivity, pagination). It is adequate but not fully transparent.

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?

Two sentences are front-loaded with purpose and parameters, followed by a sibling tool reference. Every word serves a function; no fluff.

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?

The description covers search, filtering, and returned fields, and references get_pipeline_stages. With an output schema present, return values need not be elaborated. However, the limit parameter is not addressed, and search behavior details (e.g., partial matching) are missing. Mostly complete given the tool's simplicity.

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 explains 'query' and 'stage' parameters in context ('by name and/or filter by deal stage'), adding meaning beyond the schema. However, 'limit' is not mentioned, leaving one of three parameters undocumented. Schema coverage is 0%, so the description should cover all parameters.

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 searches HubSpot deals by name (query) and/or stage, and lists the returned fields. It distinguishes from siblings like get_deal (single deal) and get_pipeline_stages (stage discovery) by mentioning the latter.

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?

Explicitly recommends using get_pipeline_stages to find valid stage values, but does not clarify when to choose get_deal over search_deals (e.g., for individual deal lookups). Provides helpful context but lacks exclusions.

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