add-time-slot

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

Without annotations, the description discloses creation and non-syncing, but lacks details on idempotency, overlap handling, or side effects, leaving gaps for a mutation tool.

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 efficiently deliver core purpose and key behavioral trait, with no wasted words and front-loaded 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?

No output schema and limited behavioral detail mean agents lack information on return values, errors, or prerequisites, making the description marginally adequate.

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 coverage is 100% and descriptions in the schema already explain each parameter. The tool description adds no extra semantic detail beyond what the schema provides.

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 it creates a time slot as an internal calendar block, and explicitly notes it does not sync to external calendars, distinguishing it from siblings like add-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 implies usage for internal-only calendar blocks by contrasting with sync behavior, but does not explicitly state when to choose this tool over alternatives like add-event.

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