hubspot_get_company_deals

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

Annotations are absent, so the description carries the full burden. It states 'READ-ONLY', which implies idempotency and safety, but does not disclose pagination, error behavior, rate limits, or output format. The description adds some safety context but lacks depth.

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 extremely concise with two short paragraphs: one for purpose and one for arguments. Every sentence is necessary and front-loaded.

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 tool is simple (2 parameters, no annotations, has output schema), the description covers basic purpose and parameter types. However, it lacks details on return values and error handling, which would be helpful for an agent.

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 0%, so the description must add meaning. It describes company_id as 'HubSpot company ID' and properties as 'Comma-separated deal properties', and provides a default. However, it does not explain valid property names or behavior if properties are invalid.

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 clearly states 'Get deals associated with a HubSpot company', which is a specific verb+resource combination. It distinguishes from sibling tools like hubspot_get_company (company details) and hubspot_search_deals (search deals) by focusing on company association.

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 versus alternatives such as hubspot_search_deals or hubspot_deal_activity_timeline. The description does not provide context for when not to use it or mention prerequisites.

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