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

The description discloses key behavioral traits: sends an invite email, the recipient joins upon acceptance, and required plan level. These add context beyond the annotations, which only provide readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. No contradiction.

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 three sentences: first states purpose and lists roles, second explains behavior (sends email, join on accept), third covers prerequisites and sibling tools. It is concise, front-loaded, and every sentence adds value.

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 3 parameters, no output schema, and 0% schema coverage, the description covers purpose, required parameters, role meanings, behavior (email sent, acceptance), prerequisites (Pro plan, host status), and alternative tools. It is complete for an agent to decide use and invocation.

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?

Although schema description coverage is 0%, the description explicitly mentions all three required parameters (event_id, email, role) and explains the role enum values with their real-world meanings (e.g., host = Producer). This adds significant meaning beyond the schema's raw enum listing.

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 the tool invites a team member to a live event by email with a specific role. It lists the role enum values and their mappings (e.g., host = Producer, promoter = Co-Host), and distinguishes from sibling tools like list_event_staff, update_staff_role, and demote_staff_to_guest.

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 specifies prerequisites: requires a Pro plan, requires event_id + email + role, and the caller must be a host. It also directs to siblings for managing existing staff, providing clear when-to-use and when-not-to-use guidance.

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