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

Annotations already declare readOnly, idempotent, and non-destructive behavior, and the description adds useful runtime behavior beyond that: lists are capped, counts represent true totals, and empty lists do not indicate missing data. The only blemish is that 'capped at 25 each' seems inconsistent with the schema's 50-row maximum for `facet_limit`.

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?

Four compact sentences, each earning its place: scope, source of slug, relationship to `fetch`, list cap behavior, and empty-list semantics. The most important scoping information is front-loaded.

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 tool with only one required parameter and no output schema, this description is complete enough for an agent to call it correctly. It names the returned sections, clarifies list limits and counts, and tells the agent how to obtain the required `slug`.

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 coverage is 100%, so the baseline is 3, but the description adds real semantic value: it tells the agent the slug comes from `search_conferences` and explains that `facet_limit` controls how many rows come back per list. The 'capped at 25' wording conflicts with the schema's maximum of 50, which slightly weakens the guidance.

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 names a specific resource and action: fetching one conference edition in full with speakers, sponsors, exhibitors, and sessions. It also distinguishes itself from the sibling `fetch` by calling itself the detailed form of that tool, so an agent can reliably tell them apart.

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?

It explicitly tells the agent where to get the slug (`search_conferences`), which tool it should prefer over (`fetch`), and how it differs from that alternative. It also preempts confusion about empty lists by explaining they are normal for upcoming editions.

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