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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The added statement 'No website is fetched or changed' largely restates those hints rather than disclosing new traits such as retrieval scope, size, or freshness characteristics.

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?

Two tight sentences with zero filler. The content enumeration comes first and the scope-limiting guarantee ('No website is fetched or changed') closes the sentence, so the most important disambiguation is front-loaded and nothing is wasted.

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 an output schema present, the description need not explain return values, and annotations cover the safety profile, so the core is complete for this simple one-parameter read tool. It is only slightly short of full completeness because it omits any routing signal toward the sibling tools that write or verify the same fixes.

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?

There is a single parameter with 100% schema description coverage; the schema itself explains businessId and points to list_monitored_businesses as its source. The description contributes no additional meaning about the parameter, which is the expected baseline when the schema does the heavy lifting.

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 uses a specific verb ('Read') and enumerates exactly what artifact is returned — current revision, source observations, confirmed facts, proposed schema/copy, installation checks — for an owned business. It distinguishes itself from website-touching siblings by stating 'No website is fetched or changed', though it never names the closest alternatives (draft_website_fixes, verify_website_fixes) explicitly.

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 clause 'No website is fetched or changed' implies this is the read path for previously saved work, which signals usage context. However, it gives no explicit when-to-use, no condition distinguishing it from draft_website_fixes or verify_website_fixes, and no prerequisites beyond what the schema supplies.

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