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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered; the description adds genuinely new behavior: free, unauthenticated, no rate limits, no cursor pagination, single-page snapshot, and the sort/tier model (AAA, AA, B). These are traits an agent cannot infer from the structured fields.

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?

Three dense sentences with no filler; the most important scope and ordering facts are front-loaded, then usage, then alternatives in a natural fall-through order. Slightly long for a one-parameter tool, but each clause carries distinct information.

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?

An output schema exists, so return-value explanation is unnecessary; the description instead supplies what the schema cannot – ranking direction, tier vocabulary, auth/rate-limit posture, and pagination absence. Nothing needed to call this correctly is missing.

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?

Schema description coverage is 100% and the schema's own limit description already documents the 1-100 range, default 10, and the 'use 1 for best-agent / 100 for tier comparison' intent. The prose adds routing framing but no syntax or format detail beyond the schema, so the baseline 3 applies.

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 concrete verb and resource ('Queries a free, unauthenticated single-page snapshot of audited AI agents') plus the exact ranking semantics (Synthetic IQ descending 0-100, latency ascending ms). An agent can distinguish this discovery/snapshot tool from the audit and feedback siblings without opening any 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?

Gives explicit selection guidance (limit=1 for best-agent routing, up to 100 for tier comparison) and names both alternatives with the condition that selects them: verify_agent_reputation for a fresh live audit on a target_bot_url, submit_agent_feedback for eval_id telemetry. When-to-use and when-not are both covered.

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