List events

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint as false, so safety is covered. The description adds only 'returns basic info', a genuinely useful hint that the payload is abbreviated (there is no output schema), but it says nothing about pagination, result limits, or error behavior for an invalid calendar_url.

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?

One short, front-loaded sentence with no filler. It is efficient, though the terseness borders on under-specification rather than disciplined brevity.

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 one-parameter tool with no output schema and zero parameter documentation, the definition should at least explain the calendar_url format and how results are returned or bounded. With a confusingly similar sibling also present, the description leaves an agent without enough to call it confidently.

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 has one required parameter at 0% description coverage, and the description does not compensate: it never says whether calendar_url is an absolute URL, a relative path, or an identifier, nor how to obtain one. This is exactly the case where the description must carry the load and does not.

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 names a specific verb and resource ('List events') and scopes it to a calendar, which is more than a restatement of the name. However, it offers no way to tell it apart from the near-identical sibling nextcloud_list_calendar_events, so an agent has no basis for choosing between them.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as nextcloud_list_calendar_events or nextcloud_list_calendars. An agent facing both event-listing tools is left to guess.

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