get_calendars

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with those. It adds useful behavioral context beyond the annotations: the POST endpoint, the queries array shape (provider, accountId, optional query), and a return-order note ('Summary first'). No contradiction.

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?

Four short, information-dense sentences front-load the purpose, then cover endpoint, parameter format, alternative routing, and output style. There is no filler or repetition.

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 one required parameter, read-only annotations, and no output schema, the description provides enough to select and invoke the tool: purpose, endpoint, input format, an alternative, and a hint about response order. It could specify exact response fields and error behavior, but it is adequate for the tool's simplicity.

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 schema has no parameter description (0% coverage), leaving the description as the sole explanation. It clarifies that queries_json is a JSON array and shows its element structure via the endpoint example, fully compensating for the bare 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 states a specific verb and resource: 'Fetch calendar metadata (colors, access role, timeZone) for accounts.' It clearly differentiates from get_calendar_lists by noting that get_calendar_lists is preferable for the sidebar list, helping an agent select among siblings.

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?

It explicitly says 'Prefer get_calendar_lists for the sidebar list,' giving a clear when-not-to-use condition. It does not contrast with all other siblings like get_colors or get_synchronized_calendars, but the context of fetching calendar metadata for accounts is clear enough.

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