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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely useful non-schema behavior: no server-side LLM call (the agent does the reasoning), and the ~5000-char truncation of body text. It stops short of explaining failure modes (JS-rendered pages, timeouts, non-HTML responses) for an open-world scraper, which keeps it from a 5.

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 purpose and returned fields are front-loaded and earn their place, but the description then re-enumerates the full 9-section template and restates update_value_prop_doc's argument list verbatim — detail that already lives in that sibling's schema. The workflow guidance is worth keeping; the verbatim field list is redundant padding.

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?

There is no output schema, so the description carries the burden of describing return values — and it does so field by field, plus the truncation limit and the downstream persistence contract. Nothing an agent needs to call this correctly, or to know what to do with the result, 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 100% and the single `url` parameter is fully documented there, including the https:// requirement. The description only implies the parameter via the example (brand.website), adding no format or validation detail beyond the schema. Baseline 3 is appropriate.

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 opens with a specific verb+resource ('Scrape a brand's homepage') and enumerates exactly what is returned — title, meta description, headings, meta tags, body text (truncated ~5000 chars), and CTA labels. This is far more specific than its siblings and lets an agent distinguish it from get_value_prop_doc or fetch_keyword_forecasts immediately.

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 explicitly states when to use it ('preferred way to build a value-prop doc'), names the alternative path (get/update_value_prop_doc), and lays out the exact call sequence: create_brand → fetch_homepage_content → analyze → update_value_prop_doc. Exclusions and prerequisites are concrete.

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