calendar_add_alarm

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

Annotations indicate non-read-only but not destructive. Description just restates the action without disclosing behavioral traits like side effects, error cases, or requirements (e.g., event existence, permissions).

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, efficient and front-loaded. No wasted words, but could be slightly more structured with bullet points.

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 simple tool with 5 parameters and no output schema, the description is somewhat adequate but lacks context on return value, validation, or interaction with other alarms. Missing guidance on when to use calendarIndex vs calendarName.

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?

Description repeats schema information (kind types, timing) but adds no new semantic meaning beyond what the schema already provides. Schema descriptions cover 60% of parameters.

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?

Description clearly states action (Add), resource (alarm to an event), and specific parameters (type and timing). Distinguishes from sibling tools like calendar_list_alarms and calendar_remove_all_alarms.

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?

No guidance on when to use this tool versus alternatives. Does not state prerequisites, when not to use, or mention other tools for related tasks.

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