get_calendars

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

With no annotations, the description carries the full burden. It states only a basic 'get' operation but does not disclose any potential side effects, permissions, pagination, error behaviors, or how results are returned. The minimal wording provides scant behavioral context.

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 a single, front-loaded sentence that is concise and easily parsed. It does not waste words, though it could have added a bit more context without harm.

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 annotations, no output schema, and minimal description, the tool leaves significant gaps. It does not clarify what 'the location' refers to, what a 'calendar' includes, or what the return value looks like. This is insufficiently complete for an agent to confidently invoke it.

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 tool has zero parameters, so the input schema is trivially complete. The description adds slightly by indicating the resource type ('calendars') and scope ('all'), but for parameter meaning this is irrelevant. Baseline of 4 applies.

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 'Get all calendars in the location' uses a specific verb and resource, and the word 'all' clearly distinguishes it from the sibling tool 'get_calendar' (singular). This makes the tool's purpose unambiguous.

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 guidance is provided about when to use this tool versus alternatives like 'get_calendar' or 'get_calendar_events'. The only implicit hint is 'all', but there is no explicit statement of scope or exclusion.

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