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

With no annotations, the description carries the full behavioral load. It does disclose the key non-obvious trait that humans participate voluntarily and can decline ('Human acceptance is mandatory'), which is genuinely useful. But it says nothing about async/blocking behavior, what identifier or status is returned, timelines, or what happens to budget on decline.

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 short sentences, zero padding, with the core purpose front-loaded and the triggering examples second. The most surprising constraint (voluntary acceptance) lands last with emphasis.

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?

Seven parameters, no annotations, no output schema, and 14% schema coverage — yet the description addresses none of the budget, deadline, or location semantics and does not say what a call produces. For a tool this configurable, the definition leaves the agent under-informed about how to fill most fields.

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?

Only 1 of 7 parameters (task) has schema description coverage at 14%. The description never mentions deadline, location, requirements, budget_amount/budget_currency, or discovery_source, so nothing compensates for the coverage gap on a mostly undocumented schema.

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: requesting voluntary human execution of a real-world task an AI cannot perform digitally. That clearly separates it from discover_humans (find humans) and get_task_status (poll), even though the siblings are never named explicitly.

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 a concrete, well-targeted list of triggering situations: physical presence, inspection, photos, reading labels, local access, verification, human judgment. It lacks an explicit when-not clause or a pointer to the sibling tools, which is what keeps it off a 5.

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