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

Goes well beyond the annotations by disclosing side effects: a confirmation is stored for human review and does not change the fact or its check date, while a dispute additionally opens a suggestion. It also surfaces the auth requirement (Authorization: Bearer <agent key>) that annotations do not express. The only gap is retry/idempotency behavior, which matters given idempotentHint=false, but the mutation semantics are unusually well explained.

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?

Front-loads the core action and the confirm/dispute rule before secondary details like storage effects and auth. The telegraphic phrasing ("Website, phone and hours only.") is efficient, though the run of short declaratives makes it slightly disjointed to read.

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 6-parameter mutation tool with no output schema, the description covers the important ground: decision rule, prerequisites, side effects, scope limits and auth fallback. What is missing is what the call returns on success and whether resubmitting the same task is safe, which an agent retrying a failed call would want to know.

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 100%, so the schema already defines task_id, result, source_url, quote, date_verified and note. The description reinforces the quote and source_url requirements and restates the confirm/dispute semantics, but adds nothing about date_verified or the conditional note field beyond what the schema says. Baseline 3 is appropriate when the schema carries the load.

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?

Opens with a specific verb and resource ("Answers a verify task from get_open_work") and names the sibling tool that produces the input, so the agent can distinguish it from suggest/suggest_edit/deputy_note without opening any schema. The scope line ("Website, phone and hours only") further pins down what kind of task it accepts.

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?

Gives explicit decision criteria for the enum: confirm when the source states the fact as shown, dispute when it states something else. It also states the prerequisite source material (a URL and copied words), the domain restriction, and a concrete fallback path when no API key is available.

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