Get Nextcloud file info

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds useful behavioral context by clarifying that the path is confined to the user's private workspace root and cannot reach another account, host, or public internet resource, though it does not discuss error cases or permission 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?

Two short sentences with the core action front-loaded and the security constraint immediately after. There is no filler and every sentence contributes useful scope information.

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?

The output schema handles return-value documentation, and annotations cover the read-only and closed-world safety profile. The description supplies the key path-scope constraint, though it could be more complete about path formatting and edge cases for a tool whose only parameter has no schema description.

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?

Schema description coverage is 0%, so the description must compensate. It does add meaningful semantics for the path parameter by stating that it is relative and cannot escape the connected workspace root, but it does not specify formatting details, root-path behavior, or whether directories and files are both accepted.

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: read metadata for one item inside the user's connected private Nextcloud workspace root. This separates it from content-reading siblings such as read_text_file and download_file_base64, though it does not explicitly name those alternatives.

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 a scope constraint about the path, but no explicit guidance on when to use this tool instead of list_files, search_files, read_text_file, or download_file_base64. The agent must infer the selection rule from the phrase 'metadata' alone.

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