add-to-calendar

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

Description mentions returning links rather than directly adding to calendar, which aligns with readOnlyHint and idempotentHint annotations. However, the phrase 'Add to calendar' could be misleading without clarification that no actual mutation occurs. Annotations mitigate this, but description could be more explicit about its read-only nature.

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?

Single sentence conveying purpose and outputs. No wasted words, front-loaded with key action and resource.

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 parameterless tool with no output schema, the description fully covers what it does and what it returns. It mentions target conference, link types, and compatible apps, providing sufficient context for an AI agent.

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?

No parameters exist, so schema coverage is 100%. Baseline for 0 parameters is 4. Description does not need to add parameter meaning.

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?

Clearly states the tool adds the ELC Conference 2026 to the user's calendar and provides specific links. Distinguishes from sibling tools like buy-ticket or find-best-conference by focusing on calendar addition.

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?

Usage is implied but not explicitly stated. The description does not specify when to use this tool versus alternatives like plan-conference-journey, or provide exclusion criteria. Context suggests it is for adding the event after decision, but lacks direct guidance.

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