hubspot_list_pipelines

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

The description does not disclose side effects, permissions, or read-only nature. The annotations contradict the tool name (destructiveHint=true for a list operation), and the description does nothing to clarify or mitigate this inconsistency.

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 short and to the point, with no unnecessary sentences. However, it is so sparse that it conveys little useful information beyond the tool name, making it insufficient for practical use.

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?

The description lacks critical context: expected output format, example usage, relation to HubSpot pipelines, and what the generic parameters do. It is not complete enough for an agent to invoke correctly without additional external knowledge.

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 parameters 'inputs' and 'message' are not explained at all. The schema provides no descriptions, and the description adds no meaning. An agent cannot infer what to pass or what these affect.

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_pipelines' on HubSpot, with a clear verb and resource. However, it relies on jargon like 'domain agent action' and 'dispatcher' that may not be immediately clear to all users.

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 on when to use this tool versus alternatives like list_crm_deals or other listing tools. The description only mentions routing and scope, not selection criteria.

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