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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false), so the description's added value is the agenda ordering of results, the time-zone semantics of session times, and the authentication prerequisite ('Cotlet API key with access to this app'). No return-format or pagination detail, which keeps it short of a 5.

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?

Front-loaded with the core action and resource, and the trailing sentences (update_session pointer, time zone, auth) each add something. Slight redundancy between the title-like first sentence and the second 'Lists the sessions...' sentence keeps it from a 5.

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 still tells the agent what comes back (time, tracks, speakers, description, agenda order), how to narrow results, the auth requirement, and the related update tool. Nothing an agent needs to invoke this correctly is missing.

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 date/track/event_id are already documented in the schema, and the description largely restates them ('Filter by day or track'). The only added meaning is the time-zone note, which concerns returned times more than parameters. 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?

States a specific verb and resource ('Lists the sessions of one event in agenda order') with scope and ordering. It is clearly distinguishable from whova_add_session and whova_update_session, which it explicitly cross-references.

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 usage context: scope to one event, filter by day or track, and route to update_session when a session_id is known. It does not compare against other read siblings such as whova_list_speakers or whova_list_events, but the differentiator (agenda sessions of an event) is clear enough.

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