hubspot_list_workflows

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

The description adds little beyond the annotations. It says 'run' and mentions routing, but does not disclose side effects, permissions, or whether it writes data. The annotations already indicate non-read-only and destructive potential, and the description does not elaborate on these aspects.

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 brief and to the point, with no redundant wording. It clearly states the action, routing, and parameters in a concise format. It could be slightly more informative but avoids unnecessary length.

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 is minimal and omits important context: it does not mention the output schema, error conditions, pagination, or any domain-specific behavior. Given the presence of many sibling tools and the complexity of domain-agent actions, this description is insufficient for an agent to confidently invoke the tool.

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?

Parameters are only described as 'Free-text objective' and 'Optional JSON string', providing minimal meaning. The schema has no descriptions (0% coverage), and the description does not specify what the objective should contain or how to format the JSON, leaving the agent with insufficient guidance.

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 it runs the 'hubspot domain agent action `list_workflows`', specifying the resource and action. It does not explicitly differentiate from generic siblings like 'list_workflows' or 'list_domain_actions', but the 'hubspot' qualifier provides enough 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?

No guidance is given on when to use this tool versus alternatives. It mentions routing through the dispatcher under JWT/tenant/company scope but that is not actionable usage guidance. There is no mention of prerequisites, alternatives, or conditions for use.

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