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

Annotations already declare read-only, idempotent, closed-world behavior, so the description's job is to add context beyond safety. It does that by disclosing the ranking basis (real web traffic) and the return payload (pricing, rank, AIWiseRank link), which matters since there is no output schema. It doesn't mention result limits or how the default limit of 8 behaves.

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 compact clauses: what it finds (with examples), what filters exist, and what comes back. Front-loaded with the core purpose and no filler sentences.

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 five parameters, high schema coverage, and no output schema, the description supplies the missing return-value information and the ranking rationale an agent needs to decide between this and siblings. Only minor gaps remain, such as the limit parameter and result volume.

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 coverage is 80%, so the schema already documents query, category, free_plan_only, and max_monthly_usd with good specificity. The description only restates those filters in shorthand and adds nothing about semantics (e.g., how budget interacts with free plans, already covered in schema), and never mentions the limit parameter. 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 specific verb and resource ("Find AI tools") plus the differentiating detail that results are ranked by real web traffic, with concrete example queries. It is clear what the tool does, though it does not explicitly distinguish itself from siblings like best_ai_tools or compare_ai_tools.

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 gives clear trigger context via natural-language need examples ("edit podcast audio", "SEO keyword research") and lists the optional narrowing filters. It stops short of naming when to prefer a sibling tool or when this tool is the wrong choice.

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