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

Annotations already declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false, so the write/open-world profile is covered. The description adds one genuinely useful non-annotation trait — the human review gate before acceptance — but omits cost, timing, and what confirm_submission actually triggers.

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 sentences, front-loaded with the core action and followed by the review constraint. Efficient with little waste, though the long enumerated list could be tightened.

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?

An output schema exists so return values need not be described, but for a 6-parameter submission tool with zero schema descriptions, the definition leaves required-vs-optional intent and the confirm_submission flag unexplained. The human-review note helps but is not sufficient.

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% across 6 parameters, so the description carries the full burden. The task examples loosely map to the 'task' field, but contact, subject, language, location, and especially the confirm_submission boolean are left entirely unexplained.

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+resource ('Request a custom physical task in Shenzhen') and enumerates concrete task types (visit, ask questions, photograph, collect/deliver, obtain catalogue). However it does not differentiate itself from overlapping siblings such as collect_or_deliver_sample or request_on_site_check, which cover some of the same errand types.

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 task examples imply when this generic errand tool applies, and 'Human review is required before acceptance' signals a submission workflow. But there is no explicit when-to-use versus the many specialized siblings, and no stated prerequisites for choosing this catch-all over them.

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