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

Annotations already cover read-only/idempotent/non-destructive/open-world, and the description adds real behavioral detail beyond them: the "context" view drops the duplicated venue block and full year histogram server-side, caps top authors, and filters placeholder clusters. It stops short of describing auth, rate limits, or when "full" is actually needed, keeping it at a 4.

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?

Purpose is front-loaded in the first sentence, key format and view semantics follow in clearly separated blocks, and the bulleted view comparison is scannable. The prose is slightly longer than strictly needed, but every sentence carries usable information.

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 description needn't enumerate return fields, and it appropriately focuses on how the two views differ in shape and what gets trimmed. Combined with annotations that carry the safety profile, an agent has everything needed to call this correctly, though the year parameter's exact semantics remain slightly underdetermined.

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 parameter burden and largely does: venue_key_or_url is explained as an opaque hash with two ways to obtain it, and view's two enum values are contrasted with their trade-offs. Year is documented only loosely ("optionally scoped to a year", "the requested `year` is always included"), which is the one thin spot.

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 venue") and immediately bounds the scope with "optionally scoped to a year". It also distinguishes itself from search_lacuna by casting that tool as the key-lookup step rather than a substitute. An agent can tell what this does without opening the 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 concrete entry guidance: find the key via search_lacuna(search_type="venue") or pass a /venue/... URL, and recommends "context" over "full" by default. It does not say when to prefer this over adjacent siblings like get_institution_context or get_resource, so the routing is clear but not exhaustive.

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