hubspot_company_activity

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

With no annotations provided, the description bears the full burden. It only notes the tool is READ-ONLY but fails to disclose other behavioral traits like required permissions, rate limits, error handling, or the structure of returned data (e.g., combination of notes and meetings).

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 very concise: one line for purpose and a structured argument list. No unnecessary words or fluff. Every sentence 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?

Considering the tool has 4 parameters (1 required) and an output schema exists, the description provides adequate parameter explanations and purpose. However, it lacks context about return format (e.g., combined or separate lists) and error behavior. It is sufficient but not comprehensive.

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 schema description coverage is 0%, so the description compensates well. It explains each parameter: company_id as 'HubSpot company ID', and clarifies that limit is 'Max items per type' and the booleans indicate whether to include notes or meetings. This adds significant meaning beyond the schema.

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 notes and meetings for a HubSpot company (READ-ONLY).' This specifies the action (get), resource (notes and meetings for a company), and distinguishes it from sibling tools like hubspot_get_company (company info) and hubspot_get_company_deals (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?

The description does not provide guidance on when to use this tool versus alternatives. There is no mention of context, exclusions, or when-not-to-use. Given many sibling HubSpot tools, the lack of usage guidance is a gap.

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