calendars_get_blocked_slots

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint false, covering safety. However, the description adds no behavioral context such as return format, whether a list is returned, or how blocked slots are defined. It contributes nothing beyond annotations.

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 extremely short, which is concise but under-specified. It does not earn its place by adding value; it simply restates the name. A phrase this brief cannot convey necessary usage or semantics.

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?

For a tool with 6 parameters and no output schema, the description is grossly incomplete. It doesn't explain what a blocked slot is, which of the owner parameters to provide, or what the response looks like. Even with schema descriptions, the tool lacks essential context for correct invocation.

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 baseline is 3. The description itself adds no extra meaning to parameters; it merely repeats the tool name. Parameters like userId, groupId, calendarId have terse schema descriptions but no additional context from the tool description.

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 'Get Blocked Slots' states a verb and resource but is vague. It doesn't define what a blocked slot is or differentiate from the similar sibling calendars_get_slots. It's barely more than the tool name, lacking domain context.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of scenarios, exclusions, or how it compares to calendars_get_slots. The description leaves the agent to infer usage from the name.

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