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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds real behavior: 30 items per page, ordering (oldest first for review queues), the assessment fallback rule (reviewer's saved one, else what the applicant claims), and per-item flagging of whether this account may approve it. That permission-awareness and sort/fallback context go beyond the annotations, though pagination limits and total counts are not discussed.

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?

Core purpose is front-loaded, but the body is one sprawling compound sentence with nested parentheticals and semicolon-chained clauses, which is hard to parse. Much of the item-content enumeration duplicates what the output schema already provides.

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?

Covers all four parameters' modes, explains the two tab families and the application_id variant, notes permission awareness, and cross-references the deciding tool. With an output schema present, return-shape detail need not be in the description, and the remaining parameter space is adequately addressed.

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 only 50%, and the description fully compensates: it maps each `tab` enum value to a concrete meaning (open, needs_info, approved, rejected, spam, retracted, all, proposals) and explains the proposals/decided split. It also conveys page size ("30 a page") and the application_id single-record mode, adding meaning the bare enum and schema fields do not.

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+resource: the applications queue for new entries (Console → Applications), and details exactly what each item contains (proposal, applicant's case, assessment, score, existing Wikidata entry, approval eligibility). It is clearly a listing tool for applications, distinguishable from entry-listing siblings such as get_entries or list_review_queue.

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?

Explains when each `tab` mode applies ("open" to review, oldest first; "needs_info" awaiting the applicant; "proposals" for quick proposals with no eligibility case) and when to pass application_id. It also routes the agent to review_submission for deciding and names propose_new_entry as the source of proposals. It never explicitly excludes or contrasts with adjacent listing tools like list_review_queue or list_my_submissions.

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