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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the bar is lower, but the description adds no behavior beyond the lookup hint. For a tool with add_*/remove_* array semantics it never says whether omitted fields are left unchanged, whether removing a non-existent interest errors, or whether the call is all-or-nothing.

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 with no filler; the core action is front-loaded and the ID-lookup hint follows. It is efficient, though the size is arguably too small for a 19-parameter mutation rather than too large.

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 19 parameters (only 2 required), partial-update semantics, and a non-idempotent hint, an agent needs to know what happens to unmentioned fields and to the add/remove lists. The description covers none of that; the existing output schema excuses it from explaining return values, but the mutation contract itself is undocumented.

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 only 47% across 19 parameters; the schema documents event_id, cover1_url_alt, logo_image_url and the add/remove arrays, but leaves name, about, email, phone, address, booth_no, web, location_id, category_ids and exhibitor_id bare. The description only reinforces the interest/service ID lookups already stated in the schema and compensates for none of the undocumented fields.

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 ('Update one exhibitor') scoped to an event, which separates it from create_exhibitor, delete_exhibitor and update_exhibitor_category that sit alongside it. It stops short of naming those siblings or describing what an update actually changes.

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 second sentence gives concrete prerequisite lookups (read_interests action 'list', read_services action 'list') for the ID-bearing array parameters, which is real routing guidance. However, it gives no guidance on when to choose this over create_exhibitor/update_exhibitor_category, or on preconditions such as the exhibitor having to exist in that event.

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