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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotent, so the mutation profile is covered. The description adds a valuable side-effect scope fact (no guests are invited on creation), but says nothing about what is returned, whether repeat calls create duplicates, or what permissions are needed.

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, zero filler, with the resource statement front-loaded and the constraint second. Nothing could be removed without losing information.

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 an 11-parameter creation tool with no output schema, the description omits what is returned — notably the event identifier needed to call invite_guests, which is the very next step it recommends. The schema covers inputs well, but the post-call picture is incomplete.

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 all 11 parameters are documented in-schema, including timezone defaults, max_guests waitlist behavior, and the guest_approval/max_guests interaction. The description contributes nothing beyond the schema, 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?

"New event page" identifies the resource and action, and naming invite_guests explicitly separates this from the guest-invitation sibling. It is slightly clipped (noun phrase rather than verb+resource), but an agent can tell what it makes and what it does not do.

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?

It gives one clear workflow hand-off (call invite_guests afterward), which is genuine usage context. But it never addresses when to use create_event versus duplicate_event, or what prerequisites/scope apply, so guidance is implied rather than complete.

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