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

Beyond the annotations, the description adds valuable behavioral detail: it does not crawl, does not accept credentials, does not modify the site, and produces a URL that requires a human to act on. This clearly sets expectations for a safe, non-invasive link-building operation.

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 short sentences with no redundancy. The core purpose is front-loaded, and each sentence contributes useful information about behavior or next steps.

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 one required parameter, 100% schema coverage, a full output schema, and strong annotations, the description is complete. It also covers the critical human-in-the-loop behavior that an agent must understand to use the tool 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 description coverage is 100%, and the single parameter websiteUrl is already described as a public website URL or host with https optional. The description reinforces that no credentials are needed but adds little parameter-level meaning beyond the schema.

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 states a specific verb and resource: 'Build a Foliora /preview URL for a public website.' It is clearly distinct from the read-only sibling tools and explains the core deliverable (previewUrl) without confusion.

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 clear context: the tool is for public websites, does not crawl, does not take credentials, and does not change the site. It also explains that the human must start the snapshot in a browser, but it does not explicitly name sibling tools as alternatives or give a when-not-to-use comparison.

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