Inspect Nextcloud capabilities

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context by emphasizing that reads come only from the user's authenticated, connected server and that the destination is the stored account connection rather than an arbitrary 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?

Two short sentences, with the core action and source constraint front-loaded. The second sentence clarifies the destination constraint without repeating the first.

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?

With annotations covering read-only/open-world behavior and an output schema covering return values, the description supplies the key missing context: authentication and connection scope. It could be slightly stronger by distinguishing this tool from related capability/app-access siblings.

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 there is no parameter semantics burden for the description to carry. The baseline for a zero-parameter tool is 4.

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 states a specific verb and resource: reading capability hints from the authenticated, connected Nextcloud server. It distinguishes the source from an arbitrary URL or public web search, but does not differentiate this tool from sibling tools such as probe_native_nextcloud_mcp or get_nextcloud_app_accesses.

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?

It gives clear usage context and an explicit exclusion: use the stored authenticated account connection, not an arbitrary URL or public web search. It stops short of naming sibling alternatives or explaining when another tool should be preferred.

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