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

With no annotations, the description carries the full burden, and it delivers real behavioral detail: the seven publication-type categories, the meaning of working papers, the identity of the directors, and the fact that case-matched results include cited_case_matches whose counts signal depth of analysis. It does not state result ordering, limits, or pagination, which is the remaining gap.

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?

Front-loaded with the core purpose, then types, then usage routing, then args — a sensible order with short paragraphs. Some redundancy between the body's type enumeration and the Args line, and the partial re-listing of types in Args is both duplicative and incomplete.

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 needn't be spelled out, yet the description still explains the notable cited_case_matches field, which is above the bar. For a zero-required-parameter listing tool with no annotations, the only missing pieces are result ordering/limit behavior and the inconsistent publication_type enumeration.

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 0%, so the description must compensate, and it does: each of the three parameters is documented with matching semantics ('partial match, case-insensitive') and cites_case gets worked examples plus a note on party-name vs. reporter-citation matching. The Args block, however, lists only four publication types while the body lists seven, leaving the enum range for publication_type inconsistent.

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 verb and resource ('List publications from the Engelberg Center') and enumerates the corpus contents, so an agent knows exactly what domain it exposes. It also contrasts itself with the sibling 'search' tool, drawing a clean boundary between browsing and querying.

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?

Explicitly names the alternative and the conditions that select this tool: 'Use this — not search — to answer what the corpus contains,' plus three concrete use cases (browse before searching, all work by an author, publications citing a case). The 'not search' exclusion is exactly the routing an agent needs.

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