list_calendly_events

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

No annotations are provided, so the description must disclose behavioral traits. It only states it lists events for the authenticated user but does not mention read-only nature, rate limits, pagination, or default behavior (e.g., whether it returns both active and canceled events).

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 a single concise sentence, which is good for front-loading. However, it is too brief given the complexity of the tool with 7 parameters and no additional context.

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?

Given the tool has 7 parameters, no required params, and no output schema, the description is too minimal. It does not explain the return format, default behavior, or how to interpret results, leaving the agent underinformed.

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 71%, meaning most parameters are described in the schema. However, the tool description itself adds no meaning beyond the schema; it does not clarify how parameters like status, sort, or count affect results.

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 the tool lists scheduled events for the authenticated user. It uses a specific verb and resource, and distinguishes from sibling tools like get_calendly_event (single event) and list_calendly_event_types (event types). However, it lacks nuance on what 'scheduled events' includes (e.g., active vs canceled).

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 vs alternatives such as get_calendly_event or list_calendly_event_types. The description does not mention filtering, prerequisites, or typical use cases.

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