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

With no annotations provided, the description carries the full behavioral burden. It discloses that the operation reads an external website, may take up to a minute or two, and produces only a draft rather than a final result. It also states the required header and plan. It could add whether existing profile data is overwritten, but the draft framing implies non-destructive intent.

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 description is compact yet information-dense. Every sentence contributes: what it does, time expectation, draft status and follow-up workflow, use case, and prerequisites. The key action is front-loaded, and there is no redundant 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?

Given there is no output schema and no annotations, the description covers the essential operational context: purpose, duration, draft nature, follow-up tools, and required preconditions. It does not explain exactly what fields get filled or how confirmation works, but the guidance is sufficient for an agent to invoke the tool and continue the workflow.

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?

The input schema already provides 100% coverage of both parameters, describing website_url as the homepage and client_account_id as coming from list_clients or create_client. The description adds little parameter-specific meaning beyond 'client's website' and reinforces client context. Baseline 3 is appropriate since 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 clearly states the tool's function: read a client's website and automatically fill in most of their brand profile. It also distinguishes the output as a draft, setting expectations against the sibling set_brand_profile. This is a specific verb+resource combination with no ambiguity.

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 description gives clear context: this is the fastest way to get a new client ready for a May run, and it must be followed by review and correction using get_brand_profile and set_brand_profile. It does not explicitly list when not to use it, but the workflow and prerequisites (May plan, X-Mako-Key header) are stated. This is clear context without formal exclusions.

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