Probe native Nextcloud MCP

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description reinforces this by stating discovery is done without invoking a native tool or contacting an unrelated destination, which is genuine added context about side effects. It stops short of describing failure behavior (e.g., whether unavailability surfaces as an error or a result field), though the output schema likely covers returns.

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?

Two short sentences with the core scope front-loaded, no filler. The second sentence's phrase "unrelated destination" is slightly vague and could have been stated more directly, but overall it earns its space by clarifying what the probe does not touch.

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-argument, read-only probe with an output schema and full annotation coverage, the description supplies enough context to call it safely. The only meaningful gap is behavioral output on failure, which the output schema presumably handles.

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 takes zero parameters, so the baseline is 4; the schema is empty and nothing in the description needs to explain inputs. The description correctly implies no arguments are required by tying the check to the already-stored account connection.

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?

States a specific verb and target: "Check MCP availability" scoped to "the user's stored Nextcloud account connection," which is more precise than a generic probe. The negative framing ("without invoking a native tool or contacting an unrelated destination") separates it from the sibling operation tools, but it never distinguishes itself from get_nextcloud_capabilities, which an agent could easily mistake for the same check.

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 phrase "Check MCP availability only on the user's stored Nextcloud account connection" implies a pre-flight/verification use case, and the note about not invoking a native tool hints at when it is appropriate. However, there is no explicit when-to-use/when-not-to-use guidance and no naming of get_nextcloud_capabilities as the alternative for capability interrogation.

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