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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds that matching happens across both templates and descriptions, which is mildly useful, but says nothing about result limits, pagination, or matching behavior. With annotations carrying the behavioral load, a 3 is appropriate.

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?

Two sentences, front-loaded with the purpose and followed by a compact concrete example; nothing is wasted. The example is somewhat redundant with the purpose sentence but earns its place by showing parameter usage.

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 two-parameter read-only search this is close to adequate, but with no output schema the description never describes what the search returns (fields, result counts, ranking), leaving the agent to guess at the response shape.

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 100% and the category enum is fully enumerated in the schema, so the baseline is 3. The example demonstrates a concrete query/category pairing, but adds no format, matching, or semantics detail beyond what the schema already documents.

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?

States a specific verb (search) and a specific resource (HighLevel automation blueprint presets and configuration templates), with the two search axes (keyword, category) called out. It is clearly separable from every sibling (enable, locations, doctor, etc.), though it doesn't explicitly name a distinction from any of them.

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?

The example invocation implies the intended usage pattern and shows both parameters in combination. However, there is no explicit when-to-use vs. when-not guidance, and no indication of what to do if the search returns nothing or how it relates to ghl_agency_tools_enable.

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