ews_get_free_busy

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

Describes operation as 'Read', indicating non-destructive behavior. No annotations provided, so description carries full burden; lacks details on rate limits, error handling, or data freshness aspects.

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, front-loaded with verb and resource, no wasted words.

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 description does not explain the format of free/busy blocks. However, the tool name is self-explanatory and sibling tools exist for richer context.

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?

Adds meaning beyond schema by clarifying that 'attendees' are email addresses. Schema coverage is 67% (start and end have descriptions), but description compensates by specifying 'attendee email addresses' for the first parameter.

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 'Read free/busy blocks' with specific resource (attendee email addresses). Distinguishes from siblings like ews_suggest_slots (suggest times) and ews_find_calendar_events (events).

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?

Implied usage for reading free/busy blocks, but no explicit guidance on when to use vs alternatives like ews_find_calendar_events or ews_suggest_slots.

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