hubspot_list_tasks

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

The description mentions 'pagination' but does not disclose any behavioral traits such as ordering, filtering capabilities, or default sorting. With no annotations provided, the description carries the full burden and falls short of informing the agent about side effects or constraints.

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, which is efficient but omits necessary details. It is front-loaded with the key verb and resource, yet earns a score of 3 for being concise at the cost of completeness.

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's simplicity and no output schema, the description should provide more context about return structure or behavior. It only mentions pagination, leaving the agent uncertain about data format and iteration.

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%, and the description does not explain any of the three parameters ('after', 'limit', 'properties'). The description adds no meaning beyond the raw schema, failing to compensate for the low coverage as required.

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 action ('List tasks') and the resource ('in HubSpot'), but it does not differentiate from similar sibling tools like 'hubspot_list_contacts' or 'hubspot_list_deals'. A score of 4 reflects clear purpose without sibling distinction.

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?

There is no guidance on when to use this tool versus alternatives (e.g., 'hubspot_search_tasks' or other list tools). The description provides no context, prerequisites, or exclusions, making it minimally useful for tool selection.

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