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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it: it never says whether the call is read-only, how results are ordered, what 'near' proximity means, or what the caller should do with a returned task. For a discovery tool meant to drive follow-up mutations via add_proof/verify/flag, that missing link is a real gap.

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?

It is a single sentence, which is efficient, but it is a loose comma-separated list with near-duplicate phrasing ('items whose values wait for independent proof, values that need proof'). The most useful information (what the tool returns) is buried mid-list rather than front-loaded.

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 three parameters, no annotations, and no output schema, the description needs to explain both the result shape and the relationship between returned tasks and the sibling action tools. It does neither, leaving the agent unsure what a task record looks like or how to act on one.

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 coverage is 33% — only 'near_id' is documented structurally — but the description partially compensates by enumerating task categories ('missing nutrients, unknown barcodes, open flags') that plausibly map to the undocumented 'kinds' array. It still never names 'kinds' or 'limit', and gives no hint about accepted kind values or the default/maximum of 5/20.

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 conveys that this returns small data-improvement jobs, and the enumerated categories (unproven values, missing nutrients, unknown barcodes, open flags) give a concrete sense of the resource. But there is no explicit verb — nothing states that it *lists* or *returns* tasks — and it never distinguishes itself from siblings like 'needs', 'verify', or 'flag', which sound closely related.

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?

'near what you are doing' is the only usage hint, and it is oblique rather than an actual when-to-use rule. There is no guidance on when to call this versus 'needs', 'verify', or 'add_proof', nor any mention of prerequisites or follow-up actions once a task is chosen.

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