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

Annotations already mark the tool as read-only, idempotent, and non-destructive, so the description adds valuable behavior beyond them: it never returns direct organiser addresses, and it declines events less than 21 days away. It also clarifies that the sponsor page and prospectus are returned only when the organiser publishes them. There is no contradiction with the annotations.

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 description is four short sentences and every one earns its place: purpose, return content, privacy constraint, and date cutoff. It is front-loaded with the tool's purpose and keeps the most operationally important constraints near the end without padding.

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 one-parameter read-only tool with no output schema, the description is complete: it states what is returned, when the request is declined, and what is never returned. An agent can safely invoke it using a slug from search_conferences and understands the key failure condition in advance.

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 schema already fully describes the single slug parameter as 'Conference slug, from search_conferences,' so schema coverage is 100%. The description reinforces that the tool handles one conference at a time but adds no new detail about the parameter's format or source beyond what the schema provides. The baseline of 3 is appropriate here.

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 leads with a clear purpose ('reach the organiser of one conference') and then states specifically what it returns: the conference page, sponsor page, and prospectus where published. It also draws a firm boundary by saying direct organiser addresses are never returned. It does not explicitly distinguish itself from get_conference, which may also return a conference page, but the organiser-reaching framing makes the scope reasonably clear.

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 intended use case is clear: use this tool when you need to approach the organiser of a single conference indirectly. It also gives an explicit when-not condition: events less than 21 days away are declined. It does not name sibling alternatives such as get_conference or events_open_for_sponsorship, but the context is enough for an agent to infer when this tool applies.

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