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

No annotations are provided, so the description carries the full behavioral disclosure burden. It adds the useful detail that humans are 'voluntary,' but it does not clarify whether this is a read-only discovery/search operation, whether it contacts or assigns humans, what permissions or privacy constraints apply, or what the result represents.

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?

The description is a single front-loaded sentence with the verb first and no redundant filler. Its brevity is appropriate, even though it leaves other gaps to be filled elsewhere.

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?

Given no annotations, no output schema, and zero schema description coverage for both parameters, the description is too thin. It does not explain return values, parameter usage, filtering behavior, or how discovery relates to the sibling tools that would likely follow it.

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 0%, so the description should compensate for the two undocumented parameters. It indirectly lists capability categories that may relate to the 'capability' field, but it never mentions the 'location' parameter or explains how either filter should be used.

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 description states a specific verb and resource ('Discover voluntary humans') and scopes it to physical-world tasks requiring human presence, perception, or judgment. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as request_human_help or get_task_status.

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 usage context: use it for physical-world tasks requiring presence, eyes, hands, inspection, photography, local access, verification, perception, or human judgment. It does not provide exclusions or explicitly name alternatives, so it falls short of full when/when-not guidance.

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