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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavioral context the annotations do not: results are 'blind' (anonymized candidate profiles), only pre-vetted and currently-available engineers appear, and the pool is geographically constrained to Latin America. It omits result-count/pagination behavior, but the page parameter carries that.

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?

A single dense sentence that front-loads the returned resource ('blind profiles of senior engineers... available now') and only then lists the filters. Every clause earns its place; nothing is padded or repeated from the title.

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 must signal what comes back, and it does (blind vetted profiles, availability, region). Combined with annotations covering safety and a fully documented input schema, an agent has enough to call this correctly; only the shape/size of the returned list is left unstated.

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%, so the schema already documents stack, level, page and min_overlap_hours with types, bounds and enums. The description restates the filter dimensions ('stack, level and US-hours overlap') without adding syntax, defaults, or semantics beyond the schema. Baseline 3 when the schema does the heavy lifting.

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 resource (blind profiles of senior engineers in Latin America who passed Ruzora's coding and interview vetting and are available now) plus the filterable dimensions, so the agent knows exactly what it returns. It stops short of naming or contrasting against a sibling such as request_vetted_shortlist or check_market_supply, which is the only thing separating this from a 5.

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 characterizes the result set but never says when to reach for this tool versus the many adjacent sibling tools (request_vetted_shortlist, check_hiring_fit, check_market_supply). No exclusions, prerequisites, or alternative routing are provided; the agent must infer usage from the resource description alone.

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