hubspot_get_company_activity

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 'Get activity history', which implies a read-only operation, but does not disclose any behavioral traits such as whether it returns a list or single object, whether it supports filtering, or if any side effects occur. More detail is needed for safe invocation.

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 a single sentence with no wasted words. It is front-loaded with the key information. Could be slightly expanded to include more detail while remaining concise, hence 4.

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 simplicity of the tool (one parameter, no output schema), the description provides the core purpose and required parameter. However, it lacks information about the return format, potential pagination, or examples of activity types. It is adequate but leaves some questions unanswered for an AI 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 100% with a single parameter 'company_id' having a description. The tool description does not add additional semantic value beyond the schema, but the schema itself is sufficient. Baseline 3 is appropriate.

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 verb 'Get' and the resource 'activity history' for a specific company. It distinguishes from sibling tools like hubspot_get_company (which likely returns company details) and hubspot_get_active_companies (list of companies). However, it could specify the type of activity for even greater clarity.

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 is provided about when to use this tool versus alternatives such as hubspot_get_company or hubspot_get_recent_conversations. The description lacks context on prerequisites, such as needing a valid company_id, or when to prefer this over other activity-related tools.

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