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

Annotations already declare readOnly=false, destructive=false, idempotent=false, and openWorld=false. The description adds one genuinely useful behavioral fact beyond them: attendees receive WhatsApp/email invitations, i.e. external side effects. It does not address permissions, reversibility, or what happens on duplicate calls.

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 compact sentences with no waste, and the core action is front-loaded. It is well sized, though it is terse enough that it could have spent the second sentence on routing rather than on capability restatement.

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?

For a 9-parameter mutation tool with a fully documented schema and annotations covering safety, the description is nearly sufficient. Remaining gaps are minor: no mention that recurrence generates instances about 12 weeks ahead (that lives only in the schema) and no statement of required permissions.

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 100% and every parameter, including the recurrenceRule variant objects and attendee sub-fields, is documented in the schema. The description's mention of attendees, location, and recurrence only restates schema content, so the 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?

States a specific verb and resource ('Create a ... event on a calendar') and scopes it as host-initiated, which distinguishes it from booking-driven event creation. It does not explicitly contrast with siblings such as neuron_create_event_type or neuron_update_event, so it falls short of a 5.

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 phrase 'host-initiated event' implies this is for organizer-created events rather than booking flows, but there is no explicit when-to-use guidance, no prerequisites (e.g. calendar must exist, host permissions), and no named alternative.

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