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

Goes well beyond the readOnly/non-destructive annotations by disclosing the owner-only sign-in requirement and that preview_url expires after an hour — both facts an agent cannot get from structured fields. It also surfaces runtime states (working = designer busy, interrupted) that affect interpretation of results. Minor gap: no note on pagination or size limits for the pages listing.

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 eligibility and entry-point guidance, and every clause carries information (fields, cost, doc links). It is somewhat run-on, packing a long field enumeration and three separate warnings into dense sentences, but there is no filler to cut.

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?

There is no output schema, so the description correctly spends its space enumerating returned fields and states. Auth, expiry, alternatives, cost, and prerequisite docs are all covered — nothing an agent needs to call this 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 coverage is 100%, so the baseline is 3, but the description adds the causal effect of the parameter: passing path returns that specific page's html, with examples implied (/ or /about in the schema). That is a small but real increment over the schema text.

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?

Names a concrete verb and resource: reads the business's Latchbell-hosted website, and enumerates exactly what comes back (pages, rev, preview_url, published state, page and browser checks, working/interrupted, designer_chat, photo library). It explicitly separates itself from upload_site_pages and site_designer_chat, so an agent can distinguish it from siblings without opening a schema.

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 an explicit entry rule ("Start here for any website request"), a positive alternative with its condition ("Prefer upload_site_pages when you can write the HTML"), and a cost warning that steers away from site_designer_chat (AI credits). It even flags a prerequisite doc read before authoring a booking/selling page.

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