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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context on its own: free of charge, per-network daily quotas that scale with trust level (anonymous vs SIWX wallet vs Alion account vs verified company), and how ranking works (role and place are hard filters, technologies score and explain themselves in each row). That is exactly the kind of information the schema cannot carry.

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?

It is front-loaded: purpose and input modes first, then ranking logic, then usage routing, then cost and quotas. Every sentence carries information, though the trust-tier quota sentence is long and could be compressed, and the trailing docs URL is a small tax on length.

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 24-parameter, zero-required, no-output-schema tool, the description covers the essentials: how to invoke it three ways, what filters bind versus rank, what a result row tells you, and the quota ceiling that could block a large sweep. Minor gap: it does not mention pagination via cursor or the 100-row paging cap that the schema hints at.

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 already 92%, so the baseline is 3. The description earns more by explaining the semantics the schema never states: that role and place act as hard filters while technologies are a ranking signal, and that the return rows carry a 'why'. Comma-list conventions and budget behaviour are repeated from the schema rather than extended.

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 opening sentence names the specific verb and resource ('The best people for one vacancy') and immediately states the two input modes (job_id/job_url or a described role). It explicitly contrasts itself with search_people, so an agent can distinguish it from its closest sibling without opening the 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?

It says plainly when to use it ('when you hire for a concrete role') and names the alternative with its own condition ('search_people when you browse'). The three accepted invocation styles are enumerated, leaving nothing to inference.

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