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

With no annotations provided, the description must carry the full burden, and it does explain the tool's output scope by itemizing the components of the criteria. However, it does not disclose behavioral aspects such as response format, pagination, or any side effects, missing an opportunity to compensate for the lack of annotations.

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 concise, single-sentence, and front-loads the core purpose before elaborating on content and context. It efficiently uses a parenthetical list to enumerate the criteria without rambling.

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?

Given the tool has no parameters and no output schema, the description does an acceptable job of explaining the tool's purpose and contents. However, it doesn't clarify potential use cases for the agent (e.g., when to check vetting criteria) or whether the criteria are versioned or can change, leaving some contextual gaps.

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 tool has zero parameters with 100% schema coverage (so the schema provides no ambiguity), and the description adds value by explaining what the returned criteria encompass. It effectively sets expectations for the output despite having no inputs to document.

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 clearly states the tool retrieves the full published vetting criteria, specifying what it includes (preconditions, universal exclusions, category rules, certifications weighting) and its role as the standard behind search_products results. It distinguishes itself from sibling tools by tying it to the broader product search ecosystem.

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 tool is used to understand the criteria behind search_products results but does not explicitly state when to use it versus alternatives. It could be clearer about scenarios where a user would need this tool, though the mention of search_products provides some context.

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