list_calendar_events

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

Only mentions pagination. With no annotations, this is insufficient. Fails to disclose that it retrieves events in a workspace, the effect of optional filters (platform, status), or any non-obvious behaviors like ordering or default date range.

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?

Extremely concise with two sentences that cover the core action and a key feature (pagination). No superfluous content.

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?

Lacks information about response format, filtering behavior, and default values. With no output schema, the description should explain what the tool returns. The presence of 7 parameters warrants more context than just 'list and pagination'.

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 71%, so baseline is 3. The description adds no extra meaning beyond the schema. The parameters workspace_id, start_date, end_date, page, per_page are already described in schema, but platform and status lack schema descriptions and are not elaborated here.

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?

Clearly states the verb 'list' and resource 'calendar events' with scope 'in a workspace'. Distinct from sibling list_* tools by resource, and from get_calendar_event by implying multiple events. However, does not explicitly differentiate itself.

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 on when to use this tool versus alternatives like get_calendar_event or other list_* tools. Does not mention conditions or exclusions for filtering.

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