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

Annotations flag destructiveHint=true and openWorldHint=true, and the description earns additional credit by spelling out the actual mechanism: without content it returns the current draft and its issues, with content the payload replaces the draft, drafting is free, and publishing is the founder's own action in the results app. It even warns never to tell the founder the site is live before they publish, which is real behavioral context beyond the annotations.

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?

The identity and read/write split are front-loaded in the first sentence, and the later sentences each add operational value (sourcing rules, free-vs-publish, the live-claim warning). It is dense and slightly long for a single paragraph, but appropriately sized for a nested content tool with no wasted sentences.

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 complex nested-payload tool with no output schema and zero required parameters, the description covers read behavior and return shape ('returns the current draft and its issues'), write/replace semantics, the sourcing constraints against invented numbers or quotes, and the publish handoff. Nothing an agent needs in order to call it 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 67%, so the baseline is 3, but the description adds genuine meaning: pages map one-to-one to a search, and each page carries title/description/headline/intro/sections/FAQs plus an App Store or ppid link, which clarifies the intent of ppid and path. It does not explain slug or appId semantics beyond what the schema states, keeping it out of the top band.

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 pair and resource: read or write the app's own small site, with concrete scope (a home page plus up to 11 search-driven pages) and the hosting target. An agent can distinguish this from app_metadata, landing_check, or content_brief without opening another schema, and the sibling keyword_research is explicitly tied in.

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 clear context for when this matters ('Most apps have no website, so this is what Google and AI answers can find and cite') and prescribes the workflow: pick each page's search with keyword_research, write from the listing/repo/reviews. It lacks an explicit when-not-to-use or a named alternative for the read-only case, so it stops short of the top band.

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