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

No annotations are present, so the description carries the behavioral disclosure burden. 'Search' and 'live' imply a read-only, current-data operation, which is useful context. However, it does not describe matching semantics, ordering, pagination, or result format, so behavioral transparency is modest rather than thorough.

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 single sentence is concise and front-loaded, with every phrase adding meaningful information about the resource and search dimensions. There is no filler or repetition of schema details.

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 simple search tool with four optional parameters and no output schema, the description plus schema is sufficient for basic invocation. However, it lacks detail on behavioral specifics (e.g., result ordering, pagination) and explicit routing relative to sibling tools, leaving moderate room for ambiguity.

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 covers query and tag explicitly, while the description adds alignment for 'verification tier' corresponding to the tier enum. Limit remains undocumented in both. With 50% schema description coverage, the description partially compensates but does not fully clarify all four parameters.

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 begins with a specific verb, 'Search', identifies the resource ('live RankCert products'), and names the search dimensions (free text, tag, verification tier). This makes it easy to distinguish from sibling tools like board_this_week and verification_stats, which are clearly not search operations.

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 tool to use when searching products by text/tag/tier, but it does not explicitly state when to prefer it over siblings or when not to use it. The context is clear by exclusion because siblings have different functional names, but the guidance is implicit rather than stated.

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