confluence_search_calendars

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the description doesn't need to repeat safety or idempotency. However, the description adds no additional behavioral context such as pagination, sorting, or result details. The openWorldHint is not elaborated upon.

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 efficiently states the tool's purpose. It avoids unnecessary words, making it concise and easy to parse.

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 search tool with one parameter, good annotations, and an output schema, the description covers the basic purpose. However, it lacks details on scope (e.g., public vs. private calendars), result behavior, or any limitations, making it minimally complete.

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 input schema provides a sufficiently detailed description for the 'query' parameter ('Search by calendar name, space name, or space key'). The description only reiterates 'by name or space' which is less specific. With 100% schema coverage, the description adds minimal value.

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 'Search Confluence calendars by name or space.' clearly states the action (search) and the resource (Confluence calendars), specifying the search criteria. It distinguishes from the sibling 'confluence_list_calendars' which likely lists all calendars, but does not explicitly differentiate or mention scope.

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 provides no guidance on when to use this tool versus alternatives like listing tools or specific calendar tools. It does not state prerequisites, context, or exclusions.

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