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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false), so the bar is lower. The description still adds useful context beyond them: speakers added to a session appear automatically (data provenance), and the call requires a Cotlet API key with app access (auth prerequisite). Return format is not described, but the tool is read-only and low-risk.

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 scoping statement is front-loaded, but the first two sentences ('Speakers of an event from the Speaker Center, with their sessions' and 'Lists the speakers of one event with the sessions each one speaks in') restate the same fact, costing a sentence without adding 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?

For a read-only list tool with full schema coverage and annotations, the description covers what is returned (speakers plus their sessions), how it is sourced, why to call it, and the auth requirement. No output schema exists, so the description adequately carries the return-value burden.

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 both parameters are already documented ('Event ID from list_events', 'Only speakers of this session'). The description implies event-scoping and session association but adds no syntax or format detail beyond the schema, making the baseline 3 appropriate.

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 speakers of one event with the sessions each one speaks in.' An agent can tell exactly what it returns without opening the schema, and it is clearly distinct from list_attendees or list_sessions siblings.

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 explicit downstream usage — 'Use it to build the recipient list for message_speakers' — which names the related tool and the condition that motivates calling it. It does not name when NOT to use it or offer competing alternatives, so it falls short of full when/when-not guidance.

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