get_freebusy

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

No annotations provided, so description bears full burden. Discloses it queries windows and requires a scope, but does not specify response format (e.g., list of time ranges per user), default behavior (free+busy vs only busy), or error handling. Minimal transparency.

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?

Short 2-sentence description is mostly concise. The leading bracketed version info '[Official API + UAT, v1.3.7]' adds some noise but does not severely impact readability.

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?

Tool has 6 parameters (3 required) and no output schema. Description does not explain the response structure (e.g., array of time ranges, per user/room), nor how to interpret results for scheduling. Incomplete for an AI agent to reliably use.

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 already covers all 6 parameters with descriptions (100% coverage). Tool description adds no extra parameter information beyond what is in schema. Baseline score 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?

Clear verb 'Query' and resource 'freebusy windows for one or more users in a time range'. Distinct from siblings like list_calendar_events which return events, not free/busy blocks. Use case 'find a meeting slot' further clarifies purpose.

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?

Explicitly states 'Use to find a meeting slot', providing a clear usage context. Mentions required permission but does not give explicit when-not-to-use or alternative tools.

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