hubspot_list_users

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

The description implies a read-only user listing operation, but the annotations mark destructiveHint true and readOnlyHint false, with no explanation of side effects. This is a direct contradiction between the action name and the declared destructive behavior.

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 avoids fluff, but part of it is tautological ('Run the hubspot domain agent action `list_users`'). The JWT/tenant/company routing note is useful but the overall content is thin.

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 key context such as what users are listed, whether the call returns the full list or requires filters, and what side effects or permissions are involved. It is minimally sufficient for a wrapper but not complete for reliable selection and invocation.

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 generic `message` and `inputs` parameters are only described as free-text and optional JSON; no HubSpot-specific fields, filters, or expected inputs are documented. This adds little beyond the schema's empty parameter descriptions.

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 identifies this as running the hubspot `list_users` action but does not state what listing users accomplishes or what kind of data is returned. It does not differentiate the tool from the many other domain-agent wrapper actions beyond the action name.

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 when-to-use guidance or alternative comparison is provided. The description only explains that the call is routed through the domain-agent dispatcher, not when an agent should choose this tool over related CRM list operations.

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