hubspot_search_tickets

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

The description adds some context beyond the annotations by explaining that calls are routed through the platform's domain-agent dispatcher and scoped to JWT, tenant, and company. However, it does not disclose what executing `search_tickets` actually does or what side effects to expect, and the `destructiveHint: true` annotation is left unexplained for a tool whose name suggests a search operation.

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 compact and front-loaded: it states what is being run, adds routing/scoping context, then lists the two arguments. Every sentence serves a purpose, and there is no redundant filler.

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?

An output schema exists, so return-value documentation is not required, but the description still omits the core behavior of the tool, when to select it over alternatives, and any clarification of the destructive annotation. For a tool in a very large sibling list, this is insufficient context 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 description gives both parameters semantic roles beyond the raw schema: `message` is a free-text objective and `inputs` is an optional JSON string of structured inputs. This is helpful but generic, and it does not say what kinds of structured inputs are valid or how the free-text message should be phrased for the HubSpot action.

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 names the exact HubSpot domain agent action being wrapped (`search_tickets`) and frames the tool as the routing entry point to it. It is clear enough to distinguish this from generic dispatcher tools, though it never explicitly states that the tool searches for HubSpot tickets, leaving the actual semantics to 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?

There is no guidance on when to use this tool instead of sibling HubSpot search/list tools such as `hubspot_search_contacts` or `hubspot_search_deals`. The description mentions routing under JWT, tenant, and company scope, but that does not help an agent decide whether this is the right tool for a given task.

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