hubspot_company_contacts

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

The description explicitly marks the tool as READ-ONLY, which is a key behavioral trait. However, no other behavioral details are provided (e.g., error handling, rate limits, auth requirements). Without annotations, the description carries the burden but provides minimal additional transparency beyond read-only.

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 with one sentence for purpose and a clear args list. Every line adds value with no redundancy. Front-loads the core functionality.

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 read-only nature and the presence of an output schema, the description covers the essentials. It could mention that the result is a list of contacts, but the output schema likely defines the return structure.

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 description coverage is 0%, so the description compensates well. It explains company_id as 'HubSpot company ID' and limit as 'Max contacts to return (default: 5)', adding meaning beyond the schema's titles and default value.

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?

Description clearly states the tool gets contacts associated with a HubSpot company, with a specific verb and resource. It distinguishes from siblings like hubspot_get_company (gets company info) and hubspot_search_contacts (searches contacts).

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?

No guidance on when to use this tool vs alternatives such as hubspot_search_contacts or hubspot_get_contact. The description lacks context on prerequisites or conditions.

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