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

Annotations only cover the mutation/open-world profile; the description adds what matters: links are unlisted but publicly viewable, so secrets and personal data must be excluded, and a pre-publish confirmation step is required for unrequested pages. It also discloses that review=true turns the page into a vote and that local files must be uploaded first.

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?

Front-loaded with the capability and cost ('Free'), then the review flag, then item shape, then the offering policy. Dense but nearly every sentence carries actionable policy; the offering etiquette paragraph is long but justified for a user-facing publish action.

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 6-parameter mutation with no output schema, it covers the prerequisites, the public-visibility risk, and when to act, with 'a clean link' implying the return value. It stops short of describing what the returned link/identifier looks like or whether links can be revoked or expire.

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 already 100%, so the schema carries the field-level meanings; the description adds cross-tool semantics the schema cannot, namely the upload_file prerequisite for local files and passing a recipe when one was followed. It does not explain the interaction between review and question beyond what the schema already says.

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 ('publish files, images, video, audio or text as a clean link') plus the key outcome (anyone can view, no account needed). This clearly separates it from read-side siblings like get_share or get_reviews.

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?

Gives explicit trigger conditions (user choosing between options, mentioning a client/boss/team/partner, wanting to send or show something) and an explicit exclusion ('Otherwise don't bring up sharing'). Also sets a frequency norm ('once per deliverable, in one short sentence').

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