apex_add_calendar

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

Annotations already indicate a non-read-only operation (readOnlyHint=false), and the description's 'Add' is consistent. However, no extra behavioral context is provided beyond what annotations convey—no mention of side effects, prerequisites, or failure modes. The only added constraint is about SQL input, not tool behavior.

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 concise sentences front-load the core purpose and a key constraint. No filler, but it could be slightly more informative without becoming verbose.

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?

The tool has 9 parameters and an output schema, but the description stays minimal. While the schema covers parameter details, the description does not address the broader context (e.g., when to prefer this over other region types, or what happens after creation). It is adequate but not comprehensive.

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%, so the schema already documents all parameters thoroughly. The description's note about date and title columns merely reinforces existing schema descriptions without adding new semantic meaning. Baseline of 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?

The description clearly states that the tool adds a calendar region, which is a specific verb + resource. It distinguishes itself from sibling region-adding tools (e.g., apex_add_region, apex_add_timeline) by naming 'calendar' as the region type, though it does not explicitly contrast them.

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 requirement 'SQL must include a date column and a title column' implies when to use this tool (with data that has date/title fields), but there is no explicit guidance on alternatives or exclusions. Usage context is implied rather than stated clearly.

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