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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the description needn't restate it. It adds the useful scoping detail that results are limited to the current organization, but says nothing about pagination, result count, or ordering.

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?

A single 10-word sentence with the resource front-loaded and zero filler. Nothing can be removed without losing the organizational-scope qualifier.

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 zero-parameter read tool whose annotations fully carry the safety profile, the description is essentially sufficient. The only minor gap is the absence of any note on pagination or the shape/count of calendars returned.

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 takes zero parameters, so per the rubric the baseline is 4. There are no argument semantics for the description to clarify, and schema coverage is 100%.

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 states a specific verb ('Retrieve') and resource ('booking calendars') with clear scope ('for the current organization'), which distinguishes it from the singular neuron_get_calendar sibling. It stops short of explicitly naming alternatives, but the resource and plurality alone make the intent unambiguous.

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?

Usage is only implied: a list operation with no parameters means it is the entry point for enumerating calendars. There is no explicit guidance on when to use this versus neuron_get_calendar or how it relates to availability/event-type tools that also touch calendars.

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