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

Annotations already declare openWorld, non-read-only, idempotent and non-destructive, so the bar is lower. The description still adds real behavioral value: no booking or charge occurs, credentials must never be included, and the returned private task token must be saved — none of which the annotations convey.

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?

Five short sentences, front-loaded with purpose, then constraints, then the token-handling instruction. Every sentence carries information an agent needs; the only minor cost is that the terse style leaves several required fields unexplained rather than that it wastes words.

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 15-parameter, 14-required submission tool with no output schema and low schema coverage, the description is thin. An agent still has no guidance on budget limits, service type selection, why three booleans must be true, or how the idempotency key should be generated beyond the regex.

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 15 parameters at only 27% schema description coverage, the description needs to compensate heavily but does not. It touches only the location constraint and a credentials warning; budget, service_id enum values, the three const-true confirmation booleans, system_access_delegated, and the idempotency key format are all left to the schema or undocumented entirely.

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 uses a specific verb and resource — 'Submit a real task request to Ron Long' — and clearly signals this creates a review request rather than a booking or charge. It is distinguishable from get_human_task_status and list_human_services, though it never names those siblings 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?

It gives clear preconditions for use: previously delegated authority, job location within 100 miles of Irvine, and a statement that this produces a review request rather than a commitment. It does not explicitly compare against the sibling tools or state when-not-to-use, which keeps it below a 5.

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