List HubSpot Contacts

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

Description adds pagination details and return structure (fields like hasMore, nextCursor) beyond the annotations. Annotations already indicate read-only, idempotent behavior, so the description complements well but could mention potential limits like API rate limits.

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?

Extremely concise: one sentence for purpose, then bullet-style args and returns. No extraneous information, front-loaded with core action.

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?

Covers purpose, parameters, and return format adequately for a simple list tool with no output schema. Missing error handling or rate limits, but not critical for selection decision.

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 details both parameters with meanings and defaults: limit with range and default, after as pagination cursor. Schema coverage is 100%, and the description adds context (e.g., default value, 'from a previous response').

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?

Clearly states 'List contacts from HubSpot CRM with pagination,' specifying the resource and action. Distinguishes from sibling tools for other entities like companies or deals.

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?

Describes when to use this tool for paginated listing of contacts. However, it does not explicitly exclude cases like searching for specific contacts, leaving the distinction to sibling tool names.

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