calendars_fetch_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 covered. However, the description adds no extra behavioral context such as pagination behavior, ordering, or that it returns a list of resources. It merely restates the function name without providing details that would help an agent understand what happens when the tool is invoked.

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 extremely concise (four words), which is front-loaded but at the cost of content. It is under-specification rather than appropriate conciseness. A single phrase cannot convey necessary usage details, making it poorly structured for an operational tool.

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 tool with 4 parameters (3 required), no output schema, and a sparse description, the context is grossly incomplete. The agent lacks information about parameter semantics, return format, pagination, and any filtering options. This is insufficient for correct invocation, even with annotations covering safety.

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 50%, with resourceType and locationId having descriptions, but limit and skip lack them. The description adds no further information about any parameter, failing to compensate for the missing schema documentation. An agent would not know the meaning of limit or skip, or what values resourceType can take beyond the enum, without additional context.

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 clear verb (List) and a specific resource (Calendar Resources), which conveys the basic operation. However, it does not differentiate from siblings like calendars_get_calendar or calendars_get_calendar_resource, and it lacks detail about the scope (e.g., which types of resources). It is adequate but not specific enough to fully distinguish this tool from related ones.

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?

There is no guidance on when to use this tool versus alternatives, no mention of filtering, pagination, or prerequisites. The description is a single phrase and offers no contextual advice for invoking the tool correctly. An agent would have no idea which scenarios call for this tool.

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