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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description's remaining content mostly describes return values (details, price, booked ranges), and since an output schema exists it earns limited credit; the 'end dates exclusive' note is the one genuinely non-obvious behavioral detail it adds.

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?

A single front-loaded sentence with no filler. Every clause (details, price, booked ranges, exclusive end dates) carries information, and the most important scope fact ('one venue') leads.

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 one-parameter read tool with annotations and an output schema, the description covers the essentials and does not need to explain return values. Minor gaps remain around failure behavior for an unknown venue_id and how it relates to the venues.search sibling, but nothing blocking.

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?

Only one parameter exists and schema description coverage is 100%, with the schema itself stating the id comes from venues.search. The description adds no syntax, format, or constraint information about venue_id, so the baseline 3 applies.

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 gives a specific verb+resource ('One venue's details') and enumerates the payload (price, booked date ranges), so the agent knows exactly what comes back. It implies the single-venue lookup role next to advertiser.venues.search but never names or contrasts with that sibling, which keeps it out of 5 territory.

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?

Usage is only implied: the 'one venue' scope suggests this is the follow-up call once you have a venue_id, and the schema hints the id comes from venues.search. There is no explicit when-to-use, when-not-to-use, or named alternative anywhere in the description text.

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