Get Nextcloud file info

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

Annotations already provide readOnlyHint=true, and the description's 'Get metadata' is consistent with a read operation. The description adds scope context ('inside the configured Nextcloud root') but does not disclose potential errors, path limitations, or other behavioral nuances. It neither contradicts annotations nor adds substantial extra transparency.

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, tightly worded sentence with no filler. It front-loads the core action and scope, making it easy to parse.

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 simple tool with one parameter and an output schema present, the description is functional but incomplete. It lacks parameter guidance and explicit usage advice, yet the output schema may compensate for return-value details. Overall, it is adequate but not thorough.

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 coverage is 0% for the 'path' parameter, and the description only names the parameter without explaining expected format (absolute vs. relative, file vs. folder, trailing slashes). The description does not compensate for the schema's lack of detail, leaving significant ambiguity about how to specify the path.

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 retrieves metadata for a single file or folder within the Nextcloud root. It uses a specific verb ('Get') and resource ('file info'), and distinguishes itself from siblings like list_files (multiple items) and read_text_file (content) by focusing on metadata.

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 use for individual file/folder metadata but does not explicitly state when to prefer it over alternatives (e.g., list_files for multiple items, download_file_base64 for content). No when-not-to-use guidance is provided, leaving the agent to infer from sibling names.

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