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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, and the description adds the gating intent (pre-spend eligibility check). However, it says nothing about what the check actually evaluates, whether the call has side effects despite not being read-only, or whether it is idempotent — a notable omission given readOnlyHint=false on a tool that reads like a query.

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?

A single front-loaded sentence with no filler; the timing constraint is stated up front and every clause earns its place.

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 one-parameter gate with no output schema and safety already covered by annotations, the description is nearly sufficient. It is missing only what a caller should expect back from the check (eligible/ineligible and why), which matters for a preflight gate.

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?

One parameter ('objective') with 0% schema description coverage, so the description carries the burden. It contextualizes the parameter as the proposed human task being evaluated, which is helpful, but gives no detail on expected format, level of detail, or length expectations.

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 and resource: checking eligibility of a proposed human task. The phrase 'before requesting a quote or spending funds' implicitly positions it upstream of human_request_quote, so an agent can roughly place it among siblings, though no sibling is named outright.

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?

Clearly states the usage context: run this prior to requesting a quote or committing funds. That gives a concrete when-to-use trigger tied to the request-quote flow, but it stops short of explicit when-not-to-use conditions or a named alternative.

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