get_calendar_lists

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

Annotations already establish readOnlyHint=true and destructiveHint=false, and the description aligns with those. It adds some useful behavioral context, such as the sidebar-list nature and that the calendar summary/name comes first, but it does not disclose return details, pagination, or any edge cases beyond what the annotations imply.

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 compact and front-loaded with the core purpose, then the usage context and request shape. All sentences add value, though the request-format sentence is somewhat terse and reads more like a code comment.

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 the single parameter and simple list operation, the description covers the key context: when to call, what request to send, and a hint about the response ordering. No output schema exists, so a bit more detail about the exact response fields would improve completeness, but the description is sufficient for basic invocation.

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?

Schema coverage is 0%, so the description carries the burden of explaining queries_json. It does this well by stating 'queries_json: JSON array' and giving the shape {queries:[{provider, accountId}]}, which adds essential meaning beyond the raw 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 action ('List calendars') and the resource scope ('for one or more accounts'), and adds the purpose of obtaining calendarId values. However, it does not explicitly differentiate this from sibling tools like get_calendars or get_synchronized_calendars, though 'sidebar calendar list' hints at some distinction.

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 gives explicit usage context: 'Call after get_user when you need calendarId values.' This tells an agent when to invoke the tool, but it does not mention when not to use it or name any alternative tools, so it falls short of a 5.

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