calendly_check_availability

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

No annotations exist, so description carries burden. It describes behavior (shows events, gaps are free slots) but does not explicitly state read-only nature, permissions, or side effects. Adequate but could be improved.

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?

Front-loaded with purpose, followed by a brief behavioral note and a well-structured parameter list. Efficient use of sentences, no redundancy. Slightly verbose in parameter section but acceptable.

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 simple read tool with 3 params and no output schema, description covers purpose, parameters, and basic behavior. Lacks return format details, which output schema would provide if present. Adequate but not complete.

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%, but description provides detailed parameter explanations: connector_name as Calendly connector, start/end_time with ISO format examples. Adds meaning beyond schema's title and type.

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?

Description clearly states it checks availability in a time range (Verfügbarkeit in einem Zeitraum prüfen), specifies it shows planned events and free slots as gaps. This is a specific verb-resource combination that distinguishes it from sibling tools like calendly_get_event_types.

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 on when to use this tool versus alternatives. Does not mention when not to use or suggest other tools for different scenarios. Implicitly assumes use for checking free slots, but no explicit context.

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