create_leave_calendar_blocks

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states that items are unsent, saved locally, and by default opened in Outlook for manual review. It also explains the two calendar items differ in visibility (Out of Office vs Free) and attendee handling. This covers key behavioral aspects, though it could mention permission requirements or reversibility.

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?

The description is concise and well-structured. It front-loads the main purpose, uses a clear bullet-point list for the two outputs, and includes critical caveats (unsent, saved locally) in a compact format. Every sentence adds value without unnecessary verbosity.

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?

Given the tool has 10 parameters with no schema descriptions, the description should provide enough context to invoke it correctly. It fails to explain how parameters map to the two calendar items, especially attendee handling and optional settings like all_day and confirmed. While the overall purpose is clear, a complex tool like this demands more parameter-level detail.

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 0%, so the description must compensate. However, it only refers generically to 'supplied attendees' without identifying which parameters (required_attendees or optional_attendees) map to which item. Other parameters like all_day, display, subject, location, and confirmed are not mentioned, leaving the agent unclear on how to set them correctly.

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 resource (Outlook calendar items) and the action (create), and explicitly lists two distinct outputs: a personal Out-of-Office blocker and a meeting notification. This is specific and distinguishes the tool from siblings like search_contacts or set_leave_defaults, which serve different purposes.

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 it is for leave review and emphasizes that nothing is sent and items are opened for manual review, which hints at when to use it. However, it does not explicitly state when not to use it or mention any alternative tools. While the context is helpful, it lacks explicit exclusions or comparisons to siblings.

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