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

Annotations already indicate this is a write operation (readOnlyHint=false). The description adds that the user must be a host, but does not disclose side effects like notifications, capacity changes, or other mutations beyond adding to the roster.

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 concise sentences that front-load the purpose and immediately convey key requirements. No extraneous words.

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?

Given 14 parameters, no output schema, and no schema descriptions, the description provides a useful overview but omits details on return values, optional parameter defaults, and the broader impact of adding talent (e.g., roster updates, integration with other tools).

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?

With 0% schema description coverage, the description partially compensates by listing some fields (name, bio, status, categories, act title, duration, contact, rider). However, several parameters (email, phone, home_base, is_speaker, description, portfolio_url) are not explicitly linked, and 'duration' is ambiguous regarding duration_minutes.

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 clearly states that the tool adds talent (performer, artist, DJ, speaker) to a live event's roster, specifying the general action and resource. However, it does not explicitly distinguish from sibling 'add_' tools like add_guest or add_event_host, which have different targets.

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 description mentions prerequisites: requires event_id + name and that the caller must be a host. It does not provide guidance on when to use this tool versus alternatives or what contexts to avoid.

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