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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description adds real value by explaining the token-cost semantics and that null means a change cannot start now, but it says nothing about result size, pagination, or ordering—notable gaps for a list-style read.

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 resource and self-contained in one sentence, with no filler. The long clause enumerating status fields ('whether it is being made or made again now') is awkward and slightly slows parsing, but it is not padded.

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 optional parameter, no output schema and closed-world annotations, the description carries the return-shape burden well by listing the fields and the null semantics. Only pagination/volume behavior is left unspecified, which is a minor omission for a small read tool.

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 'project' parameter is fully documented in the schema, including the optional-when-single-project rule. The description adds nothing about parameters, so baseline 3 applies.

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 names the resource (the business's landing pages) and enumerates the exact fields returned: id, name, address, live/draft state, build status, and token cost caps. The verb 'read' is only implied by the field enumeration, and the phrasing 'Sell's Your pages' is domain jargon, but an agent can still tell what comes back.

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?

It gives an explicit sequencing rule: 'Read it before page_again or page_change,' which tells the agent this is a prerequisite discovery call. It does not explain when not to use it or how it relates to the other read siblings, but the primary routing hint is present.

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