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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds little beyond that: the repeated 'Free. Free.' hints at cost but is noise, and it says nothing about matching behavior, result volume, or pagination for an openWorld search.

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?

It is a single run-on sentence that mixes what gets searched with a vague properties clause, and it ends with 'Free. Free.', an outright duplication that wastes space and undermines trust. The core intent is not front-loaded with a clear verb.

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?

With four parameters, one undocumented-by-both query/limit pair, and no output schema, the description should say more about what comes back (record shape, result cap) and about the limit parameter. As written it leaves key invocation decisions to guesswork.

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 coverage is 50%: object and properties are documented in the schema, while query and limit are not. The description partially compensates by explaining that matching is against words like a name or email (query semantics), but it gives no hint about the limit parameter's default or maximum and no syntax for query beyond examples.

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 conveys that this searches HubSpot records across four object types (contacts, companies, deals, tickets) matching words like a name or email, so the resource and intent are graspable. But it never uses a clear search verb and does not distinguish itself from siblings like hubspot_get, import_from_hubspot, or crm_search, which an agent must infer.

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 when-to-use or when-not-to-use guidance and no alternative tool named. An agent cannot tell from the text when to pick hubspot_search over hubspot_get or the crm_* find tools; the only added clause is a duplicated 'Free.'

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