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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds real behavioral context beyond that: the tolerated input formats (bare ID vs. full URL) and the richness of the payload (facets, provider metrics, README/card excerpt, publications with relationship types). It does not discuss auth, rate limits, or error behavior, but for a read tool that is a minor 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-loads the verb and resource, then input formats, then payload contents. The long enumeration of return fields is somewhat verbose and overlaps with the output schema, but the sentences remain information-bearing and there is no filler.

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 an output schema present, the response enumeration is redundant but harmless; the essential pieces — what the tool fetches, what identifier it takes, and the handoff to get_paper — are all present. Nothing an agent needs to call it correctly is missing.

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 parameter's meaning, and it does: the single parameter accepts either an art_... artifact ID or a resource URL containing that ID, including the exact URL shape. This adds genuine disambiguation beyond the bare 'string' schema entry.

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 resource') and enumerates the concrete artifact types (code repository, dataset, model, demo). It also names the sibling it routes to ('Pass a publication's paper_id to get_paper'), so an agent can distinguish it from get_paper without opening either schema.

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?

Clearly describes accepted input forms (an art_... artifact ID or a /resource/<slug>/art_... URL) and points to get_paper for reading linked publications, which gives usable when-to-use context. It stops short of explicit when-not guidance or alternative lookup paths for other resource types.

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