hubspot_list_campaigns

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

The description mentions routing through the dispatcher and the JWT/tenant/company scope, which is some contextual information, but it does not disclose the actual behavior such as whether the operation is read-only or destructive. Given the annotation destructiveHint=true, the description leaves uncertainty about side effects.

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 includes the parameter details, but the first sentence redundantly repeats the tool name. The routing sentence could be considered extra context rather than a clear statement of purpose. Overall, it is not poorly structured, but it could be tightened.

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 gives some context about scope (JWT, tenant, company) but omits essential details such as what the tool returns, whether it lists all campaigns, pagination behavior, or any constraints. This is insufficient for a tool with many similar siblings.

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 description provides brief explanations for 'message' and 'inputs' (free-text objective, optional JSON string), but these are highly generic and do not clarify what specific structured inputs are needed for listing campaigns. The low schema coverage (0%) is only partially compensated by these vague hints.

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 merely restates the tool name ('Run the hubspot domain agent action `list_campaigns`') without explaining what listing campaigns actually does. It does not identify the resource being acted upon or the expected outcome, making it a tautology. It also fails to differentiate this from the many sibling list tools.

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. The description does not mention use cases, prerequisites, or situations where another tool (e.g., list_crm_tasks or quickbooks_list_invoices) would be more appropriate.

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