list_calendars

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns counts and upcoming events, but it does not mention if it filters by status, requires authentication, or has rate limits. The inclusion of '[query]' is unclear and may mislead about parameters.

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 short but includes unclear element '[query]' which detracts from clarity. It is front-loaded with the purpose, but the extra token is unnecessary and potentially misleading.

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 no parameters and no output schema, the description provides adequate context for a simple list tool. It describes the key output (calendars with counts and events), though it does not specify the exact format or any filtering behavior. The '[query]' part is a minor oddity.

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 input schema has no parameters, so the description does not need to explain them. Baseline for zero parameters is 4. The description adds no parameter info, but the stray '[query]' is confusing and could imply a parameter that does not exist.

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 all available calendars with counts of services and upcoming events. It uses a specific verb (list) and resource (calendars), and the additional detail on conteo de servicios y eventos próximos distinguishes it from sibling tools like list_calendar_events or list_calendar_services.

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?

The description provides no guidance on when to use this tool versus its many calendar-related siblings (e.g., list_calendar_events, list_calendar_services). No when-to-use or when-not-to-use information is provided.

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