calendars_list

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

The description explains the `selected` field's significance and its effect on booking-page availability, providing behavioral context beyond the empty schema. However, it does not explicitly state read-only nature or authentication requirements, but these are implied by the operation type.

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 two concise sentences with no wasted words, front-loading the primary action and adding valuable detail in the second sentence.

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 description covers the core functionality and the important `selected` field. It could mention whether pagination applies or list other common fields, but for a simple list tool with no output schema, it is sufficient.

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 zero parameters and 100% schema coverage, the description adds meaningful context about what the tool returns and how the `selected` field works, which is necessary since there is no output schema.

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 'List connected calendars for the authenticated user' with a specific verb and resource. It also adds context about the `selected` field, distinguishing it from sibling tools that modify calendar selection.

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 explicit guidance on when to use this tool versus sibling tools like calendars_select or calendars_unselect. The description implies it is for viewing, but does not state alternatives or when not to use it.

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