hubspot_deal_activity_timeline

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

No annotations are provided, so the description must convey behavioral traits. It correctly declares 'READ-ONLY' and hints at a limit per activity type, but does not disclose behavior on invalid deal IDs, pagination strategy, data freshness, or authorization requirements. This is adequate but incomplete.

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 three lines: a single purpose statement followed by two parameter definitions. It is front-loaded with the key action and resource, with no wasted words. Every sentence contributes value.

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 output schema exists (not shown) and there are only two parameters, the description covers the necessary context: what the tool does and its arguments. Minor missing details like ordering of results (chronological?) do not detract significantly, but the description assumes agent knowledge of HubSpot deal activity types.

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?

With 0% schema description coverage, the description fully compensates by explaining both parameters: 'deal_id: HubSpot deal ID' and 'limit: Max items per activity type (default: 25)'. This adds meaning beyond the schema titles, which are generic ('Deal Id', 'Limit'), making parameter intent immediately clear.

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 the tool retrieves 'Notes, meetings, and calls associated with a HubSpot deal' with a 'READ-ONLY' qualifier, specifying the verb (retrieve) and resource (activity timeline for a deal). The name and description make it distinct from sibling tools like hubspot_get_deal or hubspot_get_deal_associations.

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 provides no explicit guidance on when to use this tool versus alternatives, such as hubspot_get_deal for deal properties or hubspot_get_deal_associations for linked objects. There is no mention of context, exclusions, or prerequisites, leaving the agent to infer usage from the name alone.

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