get_calendar_resources

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds the HTTP method and endpoint, but does not disclose pagination, response format, or any special limitations. No contradiction with annotations.

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: purpose, endpoint shape, parameter meaning, and usage trigger are all included in a few short sentences. The endpoint example is somewhat redundant with the parameter note, but it does not waste much space.

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?

For a simple, read-only, single-parameter tool with annotations covering safety, the description provides enough context to select and call it correctly. It could add return-value or pagination details, but these are not essential for a basic list operation.

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 only states accounts_json is a required string, with 0% description coverage. The description compensates by explaining it is a 'JSON string array' and showing the expected shape {accounts:[accountId,...]}, which is essential for correct invocation.

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 room/resource calendars for accounts, using a specific verb and resource. The phrase 'room/resource' and 'Call when booking rooms' distinguishes it from sibling tools like get_calendars or get_calendar_lists.

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 provides a usage trigger: 'Call when booking rooms.' It does not explicitly name alternatives or state when not to use it, but the context is clear enough for an agent to select this tool appropriately.

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