eb_venue

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

With readOnlyHint=true, the annotation already indicates a safe read operation. The description adds value by listing the returned fields (name, address, geo) and gives provenance for the id, which is useful behavioral context without contradicting 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?

The description is two concise sentences. The first sentence delivers the primary purpose, and the second provides supplementary context. No filler or redundancy.

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?

For a single-parameter lookup tool without an output schema, the description adequately covers what it does and what it returns. It also explains how to obtain the required id. Minor gaps like error behavior or output structure are not critical given the tool's simplicity.

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 100% with the parameter described as 'Numeric venue id'. The description compensates by explaining where to find a valid venue_id, which is helpful for an agent to construct the call correctly. This goes beyond the schema's basic type description.

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 uses a clear verb+resource structure: 'Get a venue by id' and specifies the returned fields (name, address, geo). This distinguishes it from sibling tools like eb_org_venues (list venues) and eb_venue_events (events for a venue).

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 provides clear context on when to use the tool by stating where venue ids appear (expanded events, eb_org_venues). It doesn't explicitly mention alternatives or exclusions, but for a simple lookup tool this context is sufficient.

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