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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds the search_events dependency and the action-dispatch model, but does not disclose pagination behavior or what metadata/list_categories return beyond what the output schema provides.

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 short sentences, front-loaded with the core capability and followed by the dispatch model and prerequisite. 'Dispatch via action' is slightly redundant with the schema but remains useful framing.

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 an output schema and rich annotations, return values and safety are covered. The main gap is the multi-action interface: the description never explains what each action does, which is important for an agent selecting among list, get, metadata, and list_categories.

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 high, so the schema carries most parameter documentation. The description reinforces event_id provenance but adds no meaning for action, query, category_id, location_id, is_hybrid, or exhibitor_id beyond what the schema already exposes.

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: read exhibitors and exhibitor categories for an event. It clearly distinguishes reads from the create/update/delete exhibitor siblings, though it does not enumerate the four action modes (list, get, metadata, list_categories).

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?

Provides a useful prerequisite: event_id must come from search_events. However, it only says 'Dispatch via action' without explaining when to choose list vs get vs metadata vs list_categories, and it does not route agents away from any alternative tool.

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