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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful side-effect context: no payment, no durable receipt, and specific per-client/service quota. These details go beyond the annotations and do not contradict them.

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 front-load the core action and then list constraints. Every clause carries information—scope, payment, receipt, quota—with no filler or repetition.

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 simple 2-parameter trial tool, the description plus rich schema and annotations cover the essential call constraints and quota behavior. The main omission is explicit guidance on when to prefer this over the sibling validation/preparation tools, but this is not fatal.

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 description reinforces the schema's maxItems by stating 'one supported source and one quote,' and 'supported source' points to the allowed-host constraint. However, it does not explain requireAllSources or the URL/host matching details, and with schema coverage at 50% it only partially compensates for the gap.

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 opens with a concrete action ('Try') and precisely scopes the resource: one supported source and one quote using the production extractor. The 'free' and 'one' qualifiers separate it from paid or full validation flows, though it does not explicitly name a sibling alternative.

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 description clearly situates the tool as a limited free trial with explicit quota ('2 attempts/client/UTC day'), which implies when this lightweight path is appropriate. However, it gives no explicit when-not-to-use guidance or comparison to sibling tools such as validate_evidence_request or prepare_evidence_request.

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