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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write, so the safety profile is covered. The description adds genuinely useful behavior about the 10-item batch limit and iterative continuation, but says nothing about duplicate handling, partial-failure behavior, or required permissions for a creation tool that is explicitly non-idempotent.

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?

Two short sentences, front-loaded with the core action and the batch constraint. The second sentence partially restates what the schema's maxItems description already says, which is mild redundancy, but there is no wasted prose.

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 present and 100% parameter documentation, the definition is callable as written. However, for a non-idempotent bulk-create tool it omits what an agent would want: duplicate-name behavior, what happens if a batch partially fails, and whether the caller must re-invoke with remaining batches after an error.

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%, and the schema itself already documents event_id lookup via search_events, the required name rule, UUID sources for interests/services, and the maxItems=10 continuation pattern. The description repeats the batching constraint but adds no format or validation detail beyond the schema, so baseline 3 applies.

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 states a specific verb and resource ('Create exhibitors') scoped to a provided event, which clearly separates it from create_exhibitor_category, create_sponsor, and update_exhibitor. It doesn't explicitly name those siblings, but the resource noun is unambiguous.

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?

Usage is implied: add new exhibitors to an event. No guidance is given about when to use create_exhibitor versus update_exhibitor, how to check for existing exhibitors first, or what prerequisites (event must exist) are required. The batching instruction is a procedure, not a selection guideline.

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