List Direction Papers

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description goes beyond that by disclosing a real behavioral trait: 'full' returns 'much larger' raw upstream records whose info blobs 'dominate the payload', which helps the agent reason about cost. It stops short of mentioning pagination limits or rate behavior.

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?

The opening sentence is front-loaded and the two-view breakdown is well structured as a scannable list. The parenthetical enumerations ('openalex/dblp/arxiv ids, etc.') are slightly padded but each clause carries meaning.

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 need not be explained, and the view description compensates by characterizing the payload shape. What remains thin is pagination mechanics and the alternate URL form of the cluster argument, which are gaps but not blockers for correct invocation.

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%, so the description carries the burden, and it fully documents the `view` enum with per-value payload tradeoffs. It leaves `page`, `limit`, and `cluster_id_or_url` unexplained beyond the word 'paginated', and notably never says the cluster argument also accepts a URL despite the parameter name. Partial compensation only.

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 a specific verb and resource ('Fetch paginated papers associated with a Lacuna research direction/cluster'), which is unambiguous about what comes back. It does not explicitly distinguish itself from siblings like get_direction or get_paper, so the agent must infer the boundary, but the 'papers associated with a direction' framing is clear enough.

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?

The description gives solid when-to-use guidance for the `view` option ('compact' default/recommended, 'full' only when raw metadata is needed), which is genuinely useful. However it says nothing about when to call this tool versus get_direction, get_paper, or search_lacuna, so the tool-selection guidance is only implied.

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