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

With no annotations, the description carries the full burden, and it does disclose that reading needs no membership or signing key while contributing requires joining and signing locally. However, it never states the read-only nature explicitly, says nothing about pagination despite page/page_size, and the 'project gates and future deadlines' clause is undefined.

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?

Three short sentences, but the leading sentence is dense with undefined terms and buries the core action, so the text is both wordy in jargon and under-specified in meaning. The clearest fact (no key required to read) arrives last.

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?

A read/discovery tool with no annotations, no output schema, and four fully undocumented parameters needs the description to explain filtering, pagination, and result shape. The description supplies only a partial auth note, leaving most of what an agent needs to call it correctly unstated.

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% across four parameters, including an enum status field with six values and a q string with a 200-char cap. The description adds no mapping, format, or default information for any of them, so an agent gets no help beyond the raw 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 title 'Find finalized research tasks' and phrase 'Public proved task discovery' establish a discovery/search verb+resource, but the jargon ('proved task', 'original-policy research with explicit missing later metadata') obscures what is actually returned. It does not distinguish itself from siblings like uain_tasks or uain_search_research, which likely also surface tasks.

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?

'No membership or signing key required to read' and 'join and sign locally to contribute' give a rough read-vs-contribute condition, but there is no guidance on when to use this tool over uain_tasks or uain_search_research. 'Current project gates and future deadlines apply' is too vague to act on.

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