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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds real value beyond them: how the response shape is capped (papers/authors/related_directions), the presence of truncation markers, and the relative cost of each view.

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 imperative followed by a bulleted enum breakdown; each sentence earns its place. Slightly verbose in the view bullets, but the structure makes the tradeoff scannable.

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 no prose; the description still clarifies what each view actually returns. With only one required parameter and full enum/identifier guidance, an agent has everything needed to call it correctly.

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 carry the load, and it does: it explains that cluster_id_or_url accepts a numeric ID (with an example) or a URL ending in that number, and fully characterizes the 'view' enum including default and output semantics.

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 ('Fetch a Lacuna research direction/cluster') and clarifies the domain term with its identifier form. It does not explicitly distinguish itself from close siblings like get_direction_papers or get_author_directions, so it falls just short of a 5.

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?

Gives clear guidance on the tool's own options: which view to pick, that 'context' is the default and recommended, and the cost tradeoff for 'full'. It offers no guidance on when to use this tool rather than a sibling (e.g. get_direction_papers vs this), so it stops short of explicit alternatives.

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