get_free_slots

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

Since no annotations are provided, the description carries the full burden. It identifies the operation as read-only via '[tier: readonly-owner]' and provides the endpoint, but does not disclose what happens in edge cases (e.g., no slots, invalid calendar) or any rate limits.

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?

Three concise sentences with the most important information first. Every sentence adds value: purpose, endpoint, permissions. 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?

The tool has 5 parameters (3 required), no output schema, and no annotations. The description provides the endpoint and permission tier, but lacks details on return format, pagination, error handling, or timezone behavior. Adequate but not comprehensive.

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?

With 60% schema description coverage, the schema already documents most parameters. The description adds no further detail about parameters (e.g., date format, timezone usage). It fails to compensate for the schema's gaps.

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 'Get available booking slots for a calendar within a date range', which is a specific verb-resource combination. It distinguishes from sibling tools like list_calendar_events or get_appointment by specifying it's about free slots.

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 gives an endpoint mapping and a permission tier hint, but does not explicitly state when to use this tool vs alternatives like list_calendar_events. Usage context is implied but not clarified.

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