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

Annotations already cover readOnly, idempotent, non-destructive, so the safety profile is clear. The description adds meaningful behavioral context beyond those annotations: 'Catalog matches only; does not determine certification or legal applicability,' 'No match returns an empty data array,' 'Missing required or invalid input produces an argument error,' and pagination/limits behavior. This gives the agent a good model of what happens at runtime. It doesn't state whether repeated calls with the same arguments return identical results aside from the idempotent hint, but the annotations cover that. The description is honest and consistent with the readOnlyHint.

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 a compact paragraph of seven sentences, which is appropriate for the complexity (4 params, pagination, error behavior, applicability caveat). It front-loads the purpose and required input, then covers return shape, scope limitation, no-match behavior, and error behavior in order. Each sentence adds value — no filler or repetition of the schema's parameter types. It's slightly dense and could be broken into bullets, but it is efficient and well-ordered.

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 4-parameter paginated search tool with 100% schema coverage, detailed annotations, and no output schema, the description covers most agent needs: what it returns, edge cases (no match, errors), scope limitations, and pagination guidance. It doesn't specify the exact structure of 'pagination and limits' (e.g., what next_offset looks like) or the count of records returned, but the schema indicates pages and next_offset, and the description references the returned fields. It's nearly complete; a small gap is not explaining the relationship to snapshot for consistency across pages, though the schema covers that.

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 description coverage is 100% and parameters have detailed descriptions. The description adds a little beyond the schema: it calls out that 'product' can be product OR category text and notes the literal case-sensitive substring semantics is in the schema. It clarifies the structured record fields returned (source_class, provenance, snapshot, pagination, limits), which helps understand what the parameters relate to. Given high schema coverage, the baseline is 3; the description earns a 4 by semantically framing the product parameter (product/category text) and the snapshot parameter's role, adding value beyond the schema.

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 ('Find'), resource ('CCC catalog product entries'), and search key ('product or category text'). It distinguishes itself from siblings by noting it returns structured records with provenance/snapshot/pagination, and by declaring 'Catalog matches only; does not determine certification or legal applicability' — separating it from tools like find_ccc_standard_references and find_license_catalog_items. An agent can tell exactly what this tool does without reading the schema.

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 clearly implies when to use this tool: when you need CCC catalog product entries by product/category text, and gives exclusion criteria ('Catalog matches only; does not determine certification or legal applicability'), which tells agents not to use it when certification or legal applicability is needed. It does not explicitly name alternative sibling tools (e.g., find_license_catalog_items or find_ccc_standard_references), which would make routing even clearer. The context of 'catalog entries' plus the exclusion is strong but the when-not-to-use could name named alternatives.

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