confluence_get_calendar_events

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

No annotations are provided, so the description carries the full burden. It implies a read operation ('Recupera') but does not explicitly declare read-only nature, error conditions, or expected response. The description is adequate but lacks explicit behavioral disclosure.

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, efficient sentence in Italian with no wasted words. It is front-loaded with the action and resource, and every part of the sentence contributes meaning.

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 tool has 3 parameters and no output schema, the description is somewhat incomplete. It does not describe the return format or potential errors. While the usage hint for calendarId is helpful, more context about the output would improve completeness.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining that the calendarId comes from a page with a calendar macro, which helps agents understand how to obtain it. This extra context for the required parameter justifies a score of 4.

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 explicitly states that the tool retrieves events from a Confluence Team Calendar using its calendar ID. The verb 'Recupera' (retrieve) and resource 'eventi da un Team Calendar' are specific, and the tool is uniquely positioned among siblings as the only calendar-related tool.

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?

While no explicit when-to-use or alternatives are given, the description provides a practical hint that the calendar ID is extracted from a page with a calendar macro. This indirectly guides usage, and the lack of sibling calendar tools makes it clear when to use this tool.

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