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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description reinforces this and adds one real piece of context — that it never calls search or an LLM — plus the note that submission is a separate action, but it says nothing about auth, volume, or what the task payload contains.

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 sentences with no padding; the side-effect-free guarantee and the optionality caveat are both front-loaded. Slightly dense phrasing ('a task or post') costs it a point but nothing is wasted.

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?

An output schema exists, so return values need not be explained. Still, for an unusual domain concept the description does not make clear what a verification task is or what an agent is expected to do upon receiving one, which is a real gap for correct invocation.

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?

Both parameters (task, language) are optional and 100% documented in the schema, so the schema carries the load and the baseline is 3. The description adds no information about parameter semantics or format beyond the schema.

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 names a verb ('discover') and a resource ('a small, page-grounded verification task'), but 'verification task' is unexplained jargon and the tool's actual function (fetching a task definition vs. generating one) is only implied. It never names any sibling to differentiate itself from, despite a crowding set of sibling 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?

It gives a clear when-not ('initialization and ordinary browsing do not require a task or post') and frames the call as optional, which is genuinely useful. However, it never states the positive condition for when an agent should request a task, and it does not name the submission alternative even though a submit tool exists among the siblings.

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