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

Annotations already establish read-only, idempotent, closed-world safety. The description adds genuinely new behavioral facts: the rules are 'published' and 'deterministic' (stable output, safe to cache and cite), and 'Free' signals no credit consumption — a practical cost signal not present in annotations. It stops short of describing the response format or size.

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?

Two short sentences with zero filler. The content inventory is front-loaded, followed by the single actionable instruction and the cost note, so an agent gets the essentials immediately.

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 no output schema, the description carries the burden of telling the agent what comes back, and it does so via the flag codes / severities / weights / thresholds inventory. What remains unstated is the return format and rough size, a minor gap for a static reference document.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a 0-param tool applies. The description correctly implies no input is required by presenting it as a fixed published 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 names a specific resource: the deterministic SAFE/WARN/DANGER verdict rubric, and enumerates its contents (flag codes, severities, weights, grade thresholds). This is clearly a document-retrieval tool and is distinguishable from the sibling tools (free sample, products, quote) by its subject matter, though no sibling is named explicitly.

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?

"Cite it when explaining a verdict" gives one concrete usage context, which is more than nothing. However, it offers no when-not guidance and does not contrast the tool against avasis_quote or avasis_free_sample, so an agent must infer that this is the reference lookup rather than a quoting or sampling call.

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