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

Annotations already declare a safe read operation, yet the description adds genuinely new context: 'Owners only (needs sign-in)' discloses an auth requirement, the visibility rule about live_url versus the website address until a studio site is published, and the queued → working → idle/failed state progression for a pending change. These are behavioral facts not present in the annotations or the empty schema.

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?

Everything is packed into one very long sentence with double-nested parentheses, making it hard to parse on first read. The front-loaded 'Owners only (needs sign-in)' is good, but the returned-data enumeration and the parental asides should have been split into separate sentences or bullets.

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 zero-parameter read tool with no output schema, the description is thorough about what comes back: live and draft fields, the pending-change state, earlier versions, owner photos and themes, and the visibility rule for the public URL. Only the shape of 'earlier versions' (count, ordering, pagination) is left unstated.

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?

The tool takes zero parameters, so the baseline is 4. The description adds meaning by enumerating what the returned 'plain fields' contain (headline, intro, highlights, sections, cta, theme, photo), which compensates for there being no output 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?

States a specific verb+resource: 'Read the business's simple Latchbell page', and clarifies it returns both the live version and the draft as plain fields. It does not distinguish itself from the sibling 'my_website' or 'update_page', so an agent must infer that boundary, but the core read purpose is unmistakable.

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 routes the follow-up action: 'Show the owner the draft before publishing it with publish_page', which tells the agent this is the prerequisite read in a two-step review-then-publish flow. It gives no guidance on when to prefer other page-reading siblings, but the publishing workflow is clear.

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