hubspot_deals

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It indicates a read-only listing operation, but does not mention pagination behavior, meaning of 'recent', authentication requirements, rate limits, or any other operational caveats.

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 a single focused sentence with no filler. The core action and resource are front-loaded, and every word adds relevant information.

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 simple parameter set, an output schema, and a straightforward list operation, the description is mostly complete for an agent to call the tool correctly. The main gaps are the undefined 'recent' window and absence of any usage caveats, but these are minor for this low-complexity tool.

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 input schema covers both parameters with clear descriptions, so baseline is 3. The description's mention of returned fields adds mild context but does not meaningfully enrich the meaning of 'limit' or 'format' beyond what the schema already states.

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 a specific action ('List recent HubSpot deals') on a clear resource (deals) and names the key data fields returned (stage, amount, close date, owner). This distinguishes it from the sibling hubspot_contacts and the other marketing tools.

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 phrase 'List recent' implies this is the tool for retrieving recent HubSpot deals, but there is no explicit statement about when to use it versus alternatives like hubspot_contacts. No exclusions or alternative tool names are provided.

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