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

Annotations show readOnlyHint=false, destructiveHint=false, etc. The description adds behavioral details: 'The source becomes occurrence 1; the rest are created on cadence with its tickets/promo/forms replayed.' Also states host requirement. 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?

Two sentences with no wasted words. First sentence states core function and parameters; second sentence adds critical details about behavior and requirements. Perfectly front-loaded.

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?

No output schema, but description explains what happens (source becomes occurrence 1, replayed tickets/promo/forms). It covers key aspects for a creation tool, though it doesn't mention how to later manage the series or error conditions.

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 has 4 parameters with 0% description coverage. Description explains pattern (daily/weekly/biweekly/monthly) and end (end_after or end_date). It implicitly describes source_event_id but doesn't detail constraints. Provides enough meaning beyond schema.

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's purpose: 'Turn an existing event into a recurring series' with specific pattern and end conditions. It distinguishes from sibling tools like duplicate_event and create_event_draft by focusing on series creation from an existing event.

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 provides clear usage context: requires source_event_id + pattern and host status. It implies when to use (to create a recurring series) but does not explicitly mention when not to use or alternatives, though siblings like manage_event_series exist for editing.

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