List Calendars

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

The description adds significant behavioral context beyond annotations: caching details (15 min fresh, 1 hour stale), return fields (_cache_status, _cached_at), and safety guarantee. Annotations already declare readOnlyHint=true, which the description reinforces.

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 well-structured with sections (Args, Returns), uses an emoji for quick scanning, and is concise without redundancy. Every sentence adds value.

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 the output schema existing but not shown, the description adequately describes the return format (list of calendar objects with metadata, including _cache_status and _cached_at). It covers caching, parameters, and return behavior completely for the tool's complexity.

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 schema description coverage at 0%, the description fully explains all parameters: account_id as Microsoft account ID, use_cache (default True), force_refresh (default False), adding meaning beyond the 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 the tool lists all available calendars for the user, using a specific verb ('List') and resource ('calendars'). It is distinct from sibling tools like calendar_create_calendar or calendar_list_events.

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 context about when to use the tool (e.g., read-only, safe) and caching behavior (fresh vs. stale), but does not explicitly state when not to use it or contrast with alternatives beyond the implied domain.

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