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

Goes well past the annotations: it discloses the 404 trigger (no name and no email/phone), that this read is rate-limited more strictly than other reads, and that responses carry Cache-Control: no-store and X-Robots-Tag: noindex. These are exactly the operational traits an agent needs and cannot get from readOnlyHint alone.

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?

Three tight sentences with the purpose front-loaded and behavioral caveats after. The opening sentence largely restates the title, which is the only minor redundancy; every other clause carries real 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?

No output schema exists, but the description enumerates the returned fields (name, email, phone, as written by the organizer) and covers failure and throttle behavior. An agent has everything it needs to call this correctly.

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?

The single required parameter 'slug' has no schema description (0% coverage) and the description never explains it, beyond implying the tool is event-scoped. With low coverage the description was expected to compensate and it does not.

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?

Specific verb+resource ('Get an event's organizer contact') immediately scoped to a distinct slice of event data: the name, email and phone the organizer published. That separates it cleanly from siblings like get_event and get_event_join_details, which cover broader event detail.

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 description gives clear context for when the tool applies (you want the organizer's published contact for a specific event) and states the negative condition that produces a 404. It does not name a sibling alternative or an explicit 'use X instead' rule, so it stops short of the top band.

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