ping

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is clear. The description adds value by disclosing what the tool returns: the configured server, user, calendar home, and task lists found. This goes beyond the annotations and helps the agent understand the tool's behavior.

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, information-dense sentence. It front-loads the primary purpose (verify connectivity and credentials) and then lists the return contents. No wasted words.

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 zero-parameter connectivity check tool, the description is complete. It explains what the tool does and what it returns. The only minor gap is that it doesn't explicitly state that this is a safe, non-mutating operation, but the annotations cover that. It also doesn't mention potential failure modes (e.g., what happens if credentials are invalid), but that's not essential for a ping tool.

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 tool has zero parameters, so the schema is trivially complete. The description doesn't need to explain parameters. The baseline for 0 params is 4, and the description appropriately focuses on the return value instead.

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 clearly states the tool's purpose: verify connectivity and credentials against Nextcloud CalDAV. It specifies the resource (Nextcloud CalDAV) and the action (verify), and distinguishes it from sibling tools that list or manipulate tasks. The title 'Check connection' reinforces this.

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 implies this is a connectivity/credential check tool, which is distinct from the task-management siblings. It doesn't explicitly state when to use it vs alternatives, but the context is clear: use it to verify setup before performing task operations. It could be improved by explicitly saying 'use this to test connectivity before other calls'.

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