Create share link

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

Adds real behavior beyond the annotations: default permission is read-only, no email is sent, the password is not echoed in the result, and some Nextcloud versions rewrite link permissions on create with the result reflecting the server-stored value. These are exactly the surprises an agent needs warned about for a mutation, and none of it is derivable from the hint flags.

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?

Four short sentences, purpose front-loaded, each earning its place: mechanism, default permission, absence of email, result caveats. Nothing redundant with the title or schema.

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 no output schema, the description carries the return-value burden and does so: it tells the agent the password is not in the result and that the reported permissions reflect what the server stored, which is the key ambiguity for this tool. Nothing an agent needs to call it correctly is missing.

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 100%, so the schema already documents path, label, password, expireDate and the permission bit mask with its default. The description adds the read-only default and the server-side permission rewrite caveat but no new parameter syntax or format detail, so baseline 3 applies.

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 resource ('Create a public Nextcloud share link') plus the underlying mechanism (OCS Share API, shareType 3). No sibling tool (stat, list_directory, read_file, write_file, mkdir, move, delete, search) performs this action, so it is trivially distinguishable.

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?

Usage is implied rather than stated: it is clear you call this to mint a public link, and 'Does not send email' quietly rules out an expected side effect, but there is no explicit when-to-use/when-not framing or comparison to any alternative (e.g. a user/group share tool). Minimum viable guidance.

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