crm_list_contacts

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

Beyond the annotations (readOnlyHint, idempotentHint, openWorldHint, destructiveHint false), it adds meaningful behavioral context: required OAuth scope, local denial with audit logging, no caching, archived contacts excluded, and cursor-based pagination termination. This goes well beyond the structured metadata.

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 compact and front-loaded, with each sentence earning its place. It mixes usage guidance, auth requirements, caching behavior, and pagination instructions without redundancy or filler.

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?

Despite having an output schema (so return values are covered), the description covers all operational essentials: iteration pattern, auth, rate-limit trade-off, archived-contact filtering, and pagination. This is complete for a paged list tool of moderate complexity.

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 100%, so the baseline is 3. The description adds value by explaining how the 'after' cursor is used across pages and when to stop ('stop when it comes back null'), which complements the schema. It does not add much for 'limit', but the schema already documents its range and default.

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 opens with a specific verb and resource: 'List HubSpot contacts in record-id order, one page at a time.' It clearly identifies the operation and distinguishes itself from crm_search_contacts by explicitly framing this as the paged walk-all 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 description says exactly when to use it ('to walk the whole contact set') and when not to: 'Prefer crm_search_contacts when there is a term to match on, since listing everything is slower and burns rate limit.' It names the alternative and gives the reason.

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