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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description earns credit for extra semantics not in the annotations: 'seats_left 0 is full' defines the fullness convention, and 'Times are local to the venue' resolves timezone ambiguity for returned timestamps.

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?

Two short sentences, zero filler, with the core resource stated first and the two clarifying facts (fullness, timezone) trailing. Every clause carries 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 no output schema, the description correctly compensates by sketching the return shape (sessions containing slots with seats_left) and the timezone of the values. Minor omissions remain — result ordering, whether past/dated sessions are excluded by 'upcoming', and behavior when nothing matches.

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 100%, so the four parameters (venue_id, from_date, to_date, limit) are fully documented in the schema. The description adds nothing about parameter meaning or interaction (e.g. how from_date/to_date interact with 'upcoming'), leaving it at the baseline for fully-covered schemas.

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 (List) and resource (a venue's upcoming sessions) and even describes the nested payload — slots with seats_left. It does not, however, differentiate itself from the siblings book_slot or find_venues, so an agent gets no explicit contrast.

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?

There is no when-to-use guidance, no prerequisites (e.g. that venue_id comes from find_venues, which only appears in the schema), and no mention of the sibling book_slot as the action that follows a listing. Usage is only implicitly inferable from the word 'upcoming'.

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