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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is low. The description earns credit by detailing exactly what is returned (ordering of fields, official score labels, checklist, acceptance bar), which is valuable given there is no output schema.

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, no filler: one enumerating return contents, one covering accepted input forms. The content list is dense but every item is informative, and parameter guidance is appropriately deferred to the second sentence.

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 no output schema, the description carries the return-value burden and does so thoroughly. The single required parameter is fully covered. Only the missing sibling-disambiguation (e.g. reviewers form vs LLM policy) keeps it from being complete.

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 100% for the single venue parameter and already lists examples ('iclr', 'CVPR'). The description echoes the slug/name/alias flexibility with matching examples ('iclr', 'NeurIPS', 'ACL Rolling Review', 'cvpr'), adding marginal value 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 the specific resource (the venue's reviewer form) and enumerates its contents precisely (fields, score scales, author checklist, meta-review, acceptance bar, LLM policy). It's clear what the tool returns, though it leads with a noun phrase rather than a verb and doesn't explicitly distinguish itself from the overlapping get_llm_policy sibling.

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?

There is no statement of when to use this tool versus get_llm_policy, get_deadline, or the other siblings, despite the LLM-policy overlap being an obvious source of confusion. Usage must be inferred from the content list alone.

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