List shares inside the Nextcloud workspace

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

The annotation already declares readOnlyHint=true and destructiveHint=false, but the description adds value by noting that the operation is 'credential-free' and returns metadata rather than raw content. It also clarifies that results are restricted to the configured workspace root, which is not expressed in the annotations.

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 sentence, front-loaded with the primary verb and resource. Every word contributes meaning, with no redundant content 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?

The tool is low-complexity with only two optional params, and the output schema removes the need to describe return values. However, the description still leaves parameter semantics unexplained and does not mention how many shares are returned or any filtering behavior.

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 schema has zero description coverage and the description never mentions the 'path' or 'include_subfiles' parameters. With no parameter explanations anywhere, an agent must guess at the meaning and expected format for these optional inputs.

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 names a specific verb ('List'), a clear resource ('credential-free share metadata'), and a scope ('constrained to the configured workspace root'). This distinguishes it from sibling tools like list_files, which lists files, and the various Nextcloud capability/access tools.

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 gives context ('credential-free', 'constrained to the configured workspace root') but does not explicitly state when to prefer this tool over alternatives like list_files or search_files. No alternatives or exclusions are mentioned, so guidance is implied rather than explicit.

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