hubspot_list_lists

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

Annotations already carry the safety profile (readOnly=false, destructiveHint=true, etc.), so the description does not need to repeat it. It does add one genuinely contextual detail: execution is scoped to JWT, tenant, and company. However, it provides no insight into why a 'list' operation is flagged destructive, what side effects might occur, or what the domain-agent routing means in practice.

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 not padded, but the first sentence is redundant with the tool name, and the rest is generic wrapper language. It is compact without being meaningfully informative.

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?

For a tool in a large group of similarly named HubSpot listers, this description is not complete enough to let an agent call it correctly. It leaves undefined the semantics of the 'lists' being listed, the acceptable message/input structure, and any relationship to the sibling list tools. An output schema exists, but the actor cannot reliably get there without a clearer target.

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?

With 0% schema description coverage, the description carries the full burden of explaining the parameters. It only says that message is a 'free-text objective' and inputs is an 'Optional JSON string of structured inputs'—generic boilerplate that could apply to any domain-agent wrapper. It does not explain how to construct the JSON for this specific action or what the objective should express.

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 opening sentence merely restates the tool name as 'Run the hubspot domain agent action `list_lists`', which is tautological. It never says what these lists actually are or what listing them accomplishes, and it does not distinguish itself from the many sibling `hubspot_list_*` tools such as `hubspot_list_forms` or `hubspot_list_campaigns`.

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 about when to use this tool versus alternatives. The only context is routing through a domain-agent dispatcher under JWT/tenant/company scope, which is about execution plumbing rather than when to pick this tool. An agent browsing the huge sibling list is given nothing to select it by.

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