hubspot_contacts

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

No annotations are provided, so the description carries the behavioral burden. It states the operation and return fields, but 'recent' is ambiguous (created vs. updated) and there is no mention of ordering, time window, or pagination. For a read-only list tool, this 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?

A single sentence communicates the verb, resource, scope, and returned fields with no filler. It is front-loaded and every word earns its place.

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 low complexity, full parameter schema, and output schema, the definition is mostly complete for basic invocation. The main gaps are the undefined meaning of 'recent' and the absence of any guidance on when to use this tool versus sibling HubSpot tools like hubspot_deals.

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 has 100% description coverage for both parameters (limit and format), so the schema already provides the parameter meanings. The description adds no parameter-level detail beyond listing output fields, but no compensation is needed because the schema is strong.

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 uses a specific verb ('List') and resource ('HubSpot contacts'), and enumerates the returned fields (name, email, company, lifecycle stage). It clearly identifies what the tool does, though it does not explicitly contrast it with the sibling hubspot_deals 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?

The intended use is implied: an agent should call this when it needs recent HubSpot contacts. However, there are no explicit when-to-use conditions, exclusions, or mentions of alternatives such as hubspot_deals, so the guidance is minimal.

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