Probe native Nextcloud MCP

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

Annotations already declare readOnlyHint=true, but the description adds meaningful context by guaranteeing the tool 'never invokes a native tool.' This clarifies that the probe has no side effects on the Nextcloud instance, going beyond the generic read-only hint and providing a concrete behavioral guarantee.

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 two short sentences, front-loaded with the core purpose and an important safety qualifier. Every word contributes value; there is no redundancy or filler.

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 health-check tool with an output schema, the description is fully sufficient. It explains what the tool does and its side-effect-free nature; the output schema covers return format, so no additional description is necessary.

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 description does not need to explain parameter semantics. Per the baseline for no parameters, a score of 4 is appropriate; the description adds no extraneous parameter details and relies on the schema's empty property list.

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 function: to check reachability of the Nextcloud Context Agent MCP. It uses a specific verb ('Check') and a clear resource, and explicitly notes it 'never invokes a native tool,' distinguishing it from sibling tools that perform native actions.

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 safe, non-invasive probe, but it does not explicitly state when to use it versus alternatives or provide criteria for when it should be preferred. The 'never invokes a native tool' note is a constraint rather than direct usage guidance, leaving room for the agent to infer applicability.

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