hubspot_list_subscriptions

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

Annotations already carry the destructiveHint=true, readOnlyHint=false, and idempotentHint=false signals, so the description does not need to repeat them. It adds useful routing/scope context, but it does not clarify why a 'list' action is marked destructive or explain any side effects. There is no direct contradiction with the annotations.

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 front-loaded: action name, routing context, then a compact arg list. There is no filler or redundant restatement of the schema, and it stays within a reasonable size for a wrapper-style tool.

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 output schema and annotations cover return values and safety hints, but the description remains vague about what the tool actually surfaces. It does not specify what 'subscriptions' means, what the inputs JSON should contain, or how to compose the message. For a generic domain-agent dispatcher wrapper, this is not enough for an agent to invoke it confidently.

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?

Schema description coverage is 0%, so the description must carry the parameter-semantics burden. It provides only generic definitions: 'message: Free-text objective' and 'inputs: Optional JSON string of structured inputs.' These do not explain what fields the structured inputs should contain or what objective text should be provided for list_subscriptions specifically.

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 first sentence identifies a specific verb and resource: 'Run the hubspot domain agent action `list_subscriptions`.' The name and action make the basic purpose clear, but the description does not explain what 'subscriptions' refers to in HubSpot or distinguish this from sibling list tools like hubspot_list_campaigns or hubspot_list_workflows.

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. The description only says it routes through the domain-agent dispatcher under JWT, tenant, and company scope, which explains context but not selection criteria. With many hubspot_list_* siblings, an agent gets no help choosing correctly.

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