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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Get Calendly bookings and links,' which implies a read operation but gives no details about scope, return format, authentication, or potential limitations. This is insufficient for a tool with zero annotation support.

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, short sentence ('Get Calendly bookings and links.') with no filler or redundant content. Every word contributes to the meaning, making it highly concise and appropriately front-loaded.

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?

Despite being a simple tool with no parameters or output schema, the description is too vague to be complete. The sibling tool 'get_calendly_links' suggests a potentially overlapping function, and the description doesn't clarify what 'bookings and links' means structurally or whether the response includes combined data. The lack of output schema and annotations makes this description minimally viable at best, but the ambiguity with the sibling lowers its completeness.

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?

The tool has zero parameters, and the input schema is an empty object. Per the rubric, 0 params receives a baseline of 4. Since there are no parameters to explain, the description adds no parameter-related value but also doesn't need to.

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 uses the verb 'Get' with resource 'Calendly bookings and links,' making the core action clear. However, it does not explicitly distinguish from the sibling tool 'get_calendly_links,' which could cause confusion about whether this tool returns both bookings and links or just links.

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 like get_calendly_links or cancel_calendly. The description does not mention any use cases, prerequisites, or exclusions, leaving the agent to infer the appropriate context.

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