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

Annotations already declare openWorldHint=true and idempotentHint=true, so the description's added value is the 'nothing is scheduled, dispatched or charged' clause, which correctly tells the agent that submitting is non-binding and safe to retry conceptually. It does not address auth (conversation_token/conversation_id) or what happens after submission, but the core behavioural caveat is disclosed.

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?

Two short sentences, no filler, with the core action stated first and the non-binding caveat immediately after. Nothing is wasted.

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 22-parameter, open-world, write-shaped tool with no output schema and sparse schema descriptions, a two-sentence description leaves the agent without guidance on required identifiers, mutually exclusive fields, or what the response will contain. It covers the concept but not enough to call the tool correctly without reading the schema carefully.

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?

With 22 parameters and only 14% schema description coverage, the description carries most of the burden and supplies almost nothing — it never mentions objective vs problem_statement, budget, deliverables, or the required conversation_id/client_request_id. Only indirectly, the 'nothing... charged' phrase reinforces that budget fields are indicative, which is a thin contribution.

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 gives a concrete verb and object: asking a person to observe real-world conditions, with a parenthetical alias (Human World Oracle). It is clear on its own, but it does not differentiate itself from near-neighbours like request_sensory_report, request_independent_witness, or request_human_embodiment, all of which also ask humans for real-world information.

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 'Inquiry only' framing implies this is the lightweight, non-committal request path, which is a useful hint about when to reach for it. However, it never names an alternative tool or an explicit condition that selects this over the many other request_* siblings, so the agent must infer the routing.

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