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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral context beyond them: custom quotes, payments disabled, and no system access granted — useful constraints an agent would not otherwise know. It stops short of describing the result payload.

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 clauses with the scope front-loaded and constraints after; nothing is padded. The terse, telegraphic phrasing ('Custom quotes; payments disabled.') borders on cryptic but stays compact.

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?

With no output schema, the description should hint at what comes back; 'services ... and intake requirements' gestures at the fields but gives no structure, pagination, or format. The behavioral constraints compensate partially, but an agent still doesn't know the shape of the response.

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?

The tool takes zero parameters, so per the baseline this scores 4. The description correctly frames the scope (fixed geography, fixed provider) as intrinsic rather than something the caller can vary.

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 ('List') and resource ('human infrastructure services') plus a geographic scope (within 100 miles of Irvine, CA) and includes intake requirements. The resource term is somewhat idiosyncratic jargon, but an agent can tell this is a catalog-listing tool and not the sibling request/status tools.

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?

There is no explicit when-to-use guidance, no mention of the siblings request_human_task or get_human_task_status, and no stated preconditions. Usage is only implied by the fact that it lists services.

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