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

Annotations already cover the read-only, non-destructive safety profile. The description adds modest behavioral context by noting that colors and capacities are returned only 'when present,' but it does not disclose pagination, response shape, or any other runtime behavior.

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 sentence with no filler. The core action and scope come first, and the optional output details are appended compactly.

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 simple read-only list with one required parameter, the description plus schema and annotations are nearly sufficient. The only slight gap is the absence of a pointer to manage_tracks/manage_rooms when modification is needed, but this does not block correct invocation.

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 schema already documents both eventId and org. The description does not need to add parameter-level detail, and the term 'event's' aligns with the documented eventId.

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 specific verb ('List') and resource ('an event's tracks and rooms') and adds distinguishing details (track colors, room capacities). It clearly separates this read-only lookup from sibling management tools like manage_tracks and manage_rooms.

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 read-only phrasing ('List') implies this is the lookup counterpart to manage_tracks/manage_rooms, but no explicit when-to-use or when-not-to-use guidance is given. An agent can infer usage from the name and readOnlyHint, but the description itself does not say which alternatives to prefer.

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