publish_link

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

With no annotations, description carries full burden. It discloses permanent nature, public default, visibility controls, and security warning. Does not mention response format or rate limits, but covers key behavioral aspects.

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?

Three sentences, front-loaded main action, then options and exclusions. No redundancy, every sentence adds value.

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 7-parameter tool with no output schema and no annotations, description covers core function, supported types, visibility, and security. Lacks explanation of title parameter and return value, but overall sufficient for agent to use correctly.

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 57% (not high/low). Description adds meaning beyond schema: clarifies supported modes (text types) and visibility interaction with password/email. Does not explain title or shareEmails explicitly, but provides useful context.

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?

Description clearly states it publishes text-based content to a permanent whamlink URL, specifying supported types (HTML, Markdown, plain text) and explicitly ruling out PDF/images. It distinguishes from siblings (delete, list, replace, etc.) as the only creation tool.

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?

Explicitly says when to use (text publishing) and when not to use (PDF/images, secrets). Provides alternative (dashboard/multipart API). Covers visibility options for gating content.

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