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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds real value beyond that by disclosing pagination and exactly what the compact view strips away (raw upstream info blob, levels.cluster internals) versus what full retains.

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-loads the tool's core action in one sentence, then uses a tight bullet list keyed to the view values. No filler; every clause either names a view option or explains what it changes in the payload.

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-value documentation is not required, and the description still usefully characterizes the two response shapes. The remaining gap is pagination mechanics (meaning of page/limit defaults), but for a read-only list tool this is close to 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 description coverage is 0%, but the description thoroughly explains the 'view' enum (both values, default, tradeoffs), which is the highest-risk parameter. However, page, limit, and especially the string-or-integer cluster_id_or_url (which accepts a URL or id) are left entirely undocumented, so it only partially compensates for the missing schema descriptions.

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 (fetch) and resource (paginated papers associated with a Lacuna research direction/cluster) with clear scope. It is easily distinguishable from siblings like get_direction (the cluster itself), get_paper (single paper), and get_author_papers (papers by author).

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 guides the view choice: 'compact' is the default and recommended for citation-ready rows, 'full' only when raw upstream metadata is needed. This is strong when-to-use guidance for the main decision, though it never contrasts this tool against alternatives like search_lacuna or get_direction.

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