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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false), so the bar is lower, yet the description still adds real behavioral detail: server-side removal of the duplicated institution block, author capping in the compact view, and explicit truncation metadata in the full view. It does not mention auth needs or rate limits, but the shape differences are genuinely useful context beyond the annotations.

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 purpose, then a scannable two-bullet breakdown keyed to the view enum, then the routing sentence. Slight redundancy between "duplicated institution block dropped server-side" and "duplicated institution record," but no filler sentences.

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 spelled out, and the description still usefully characterizes the two response shapes and their truncation behavior. The only meaningful gap is the format of institution_key_or_url, which is required for every call and never described.

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 must carry the load. It does this well for view, explaining the semantic difference between the two enum values (compact vs. complete, and which is recommended), but institution_key_or_url is never addressed — it is not stated whether a raw key, a full URL, or both forms are accepted, leaving half the parameters undocumented.

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 agent-oriented context for a Lacuna institution") and immediately distinguishes itself from the closest sibling by naming get_institution_authors for complete author lists. An agent can separate this from get_institution_authors or get_venue_context without opening any 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?

Gives clear routing guidance: the default "context" view is explicitly labeled recommended/compact, and author pagination is explicitly delegated to get_institution_authors. It lacks an explicit when-not-to-use case (e.g., when the agent only needs a venue or author), so it falls short of a 5.

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