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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value by enumerating the exact fields returned in each result row — critical since there is no output schema — plus the AND semantics of filters and the underlying endpoint. It omits default ordering/page-size behavior, but that is documented per-parameter in the schema.

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?

Front-loaded with purpose, then the filter-combination rule, then the return-field list that substitutes for a missing output schema. The 16-field enumeration is long but earns its place; only the trailing raw endpoint adds marginal value.

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 0 required params among 22, full schema coverage, and no output schema, the description supplies the two things an agent would otherwise lack: what comes back and how filters interact. Pagination and defaults are delegated to the schema, which is acceptable here.

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 100%, so the baseline is 3, and the description adds cross-parameter semantics the schema cannot express: all filters are optional and combine conjunctively. That combinatorial rule meaningfully affects how an agent composes a call.

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 and resource ('Search the product catalogue') and differentiates from the sibling brightpearl_get_products by scope (search vs. full details). An agent immediately knows this is the lookup tool and which tool returns richer records.

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?

Explicitly says every filter is optional and combines with AND, and names the alternative ('Use brightpearl_get_products for full details'). It does not spell out when-not to use it (e.g., searching by exact id vs. product_ids), but the context for selection is clear.

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