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

With no annotations provided, the description carries the disclosure burden. It does reveal that paid content is not read and only metadata fields are searched, which is useful. However, it does not mention matching behavior, result limits, sorting, or error conditions.

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?

One clean sentence that front-loads the action and target, with no wasted words. Every phrase contributes: what is searched, what fields, and what boundary is respected.

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 single-parameter search tool, the description covers purpose, scope, and the paid-content boundary, while the schema handles the input constraint. The lack of an output schema leaves the return shape unspoken, but the tool name and described search fields make it predictable.

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 schema provides only a required 'query' string with length bounds and no description. The tool description compensates by explaining what the query searches across (IDs, titles, summaries) and what it does not access, giving the parameter operational meaning despite 0% schema coverage.

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?

Description states a specific verb ('Search') and precise resources ('product IDs, titles, and human-written summaries'). The qualifier 'without reading paid content' separates it from read_paid_product and other content-fetching siblings, making the purpose unmistakable.

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 description implies this is the query tool for product metadata, but it does not explicitly contrast with list_products or read_free_product. An agent can infer appropriate use, but there are no when-to-use/when-not-to-use statements.

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