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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered. The description adds real behavioral detail beyond that: it explains how budget ('free' filters, 'low' re-ranks) and team size (enterprise tools ranked last) affect the ranking, and what the result contains (ranked tools with reasons, pricing notes, Coghelm links). No output schema exists, so this return-format disclosure is genuinely useful.

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, front-loaded with purpose and examples before constraints and return format. No filler; each sentence adds routing, constraint, or output 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?

With readOnly annotations and no output schema, the description covers the essentials: what it recommends, the optional constraints' effects, and the shape of the response. Only minor gaps remain, such as pagination or tie-breaking behavior, which are not critical here.

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 100%, so the baseline is 3, but the description adds meaning the schema lacks: it explains the ranking behavior of 'free' vs 'low' budget values and how team_size reorders results, rather than merely restating 'Budget constraint; default any'. It also notes job accepts a slug from list_jobs.

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 ('Recommend AI tools for a job a leader needs done') with concrete examples ('run better 1:1s', 'write a board update'). The recommendation framing clearly separates it from search_tools and compare_tools, so an agent can route without opening schemas.

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?

Usage context is implied by the examples and the 'job a leader needs done' framing, but it never states when to prefer this over siblings like search_tools, get_job_guide, or compare_tools, nor any when-not condition. Adequate but leaves the alternative-selection decision to inference.

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