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

With no annotations, the description carries the full behavioral burden and does substantial work: it discloses the read-vs-write switch keyed on `content`, that writing is free, that publication is out of scope for this tool, and a hard safety rule ('Never tell the founder it is live before they publish'). It does not state whether a write overwrites vs merges beyond the schema's note, nor any auth/rate-limit behavior.

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 what the tool is before any workflow advice, and nearly every sentence carries operating information (keyword selection, sourcing constraint, publish boundary, the not-live warning). It runs slightly long with clause-stacked sentences, but there is no filler.

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 nested, mutation-capable tool with no annotations and no output schema, the description covers purpose, mode switching, sourcing rules, and the publish boundary well. The remaining gap is the shape of what a read returns ('the current draft and its issues' is undefined), which matters given there is no output schema to fall back on.

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 a moderate 67%, and the description adds genuine meaning over the schema: it explains the read/write semantics of `content` (absent = return draft and issues), that `slug` is the subdomain set on first use, and that each page carries a `keyword` linking to an App Store page or `ppid`. appId is left entirely to the schema, which keeps it out of 5 territory.

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 specific verb pair (read or write) and the exact resource: the app's small marketing site on <name>.shipfound.site with a home page plus one page per search. The prose description of page anatomy (title, description, headline, intro, sections, FAQs, ppid links) is specific enough to separate it from siblings like app_metadata or site_fixes without opening the 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 workflow prerequisite ('Pick each page's search with keyword_research; write from the listing, the repo and the reviews') and an explicit branch condition ('Without `content` it returns the current draft and its issues'). It also routes the publishing step to another surface ('publishing is the founder's own action in the results app'). It doesn't state when to prefer this over site_fixes, so it stops short of a 5.

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