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

Beyond the annotations (which already flag a non-read-only, open-world, idempotent write), the description discloses credit cost, the low-confidence confirmation path, and concrete auth options (OAuth or Bearer acd_live_ key with a URL). This is behavior an agent cannot infer from the structured fields and is directly needed to call it successfully.

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-loads the core action and extracts before the auth block, and every sentence carries information. The OAuth/API-key sentence is dense but necessary; overall it is close to optimally sized with minor verbosity in the auth instructions.

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, full parameter documentation, and annotations present, the description covers cost, auth, and the confirmation path. It leaves mode selection (product vs app) to the schema, which is acceptable, so completeness is high but not exhaustive.

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%, so the baseline is 3, but the description adds meaning by tying the persist flag to the low-confidence confirmation behavior and clarifying what the read produces. It does not elaborate on the product/app mode distinction beyond what the schema says.

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 (read website, save profile) and enumerates exactly what is extracted (name, value props, CTA, tone, product images). This clearly distinguishes it from the sibling list_brand_profiles, which reads rather than creates profiles.

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 operating context: no credit cost, low-confidence reads are surfaced for confirmation instead of saved, and sign-in prerequisites are spelled out. It stops short of explicitly naming an alternative tool or a 'when not to use' condition, so it lands just below the top band.

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