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

Annotations already declare the tool read-only, idempotent, and non-destructive; the description adds useful context beyond that: it is free, accepted evidence gets public credit, and returned tasks are filtered by staleness or low confidence. No contradiction with the annotations.

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?

The description is compact: three sentences plus an example, with the trigger condition front-loaded. Each sentence adds meaningful information, and the inline JSON example is helpful, though slightly dense.

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 read-only tool with two optional parameters and no output schema, the description covers the selection criteria, output contents, cost, public credit, and an example. It is missing explanation of each kind value and limit's default behavior, but these are minor gaps for successful 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?

Schema description coverage is 0%, so the description must compensate for parameter meaning, but it only provides one example kind and does not explain the three enum values or the limit parameter. An agent can infer that 'kind' selects task type from the example, but the meanings of find_counter_evidence and confirm_or_refute_shift are left unexplained, and limit's behavior is unaddressed.

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 action ('list'), a clear resource ('open verification tasks'), and precise scoping ('stale or below high confidence, on New Runtime patterns and shifts'). It goes beyond the title by specifying what each task entry contains, though it does not explicitly differentiate from 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?

Starts with an explicit trigger: 'Use when you can contribute evidence.' It also tells the agent that accepted evidence is credited publicly and that the response indicates which submit tool to use, which orients the agent to when this tool is appropriate. It does not name specific alternatives or exclusions, but the usage context is clear.

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