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

Annotations declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true; the description adds genuinely new behavior beyond that — automatic approval of the guide on strong signal versus a draft on weak signal. It does not explain the destructive/idempotency implication (what happens to an existing guide if this is called again, or what the guide contains), which is the one gap for a mutation tool.

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?

Dense but front-loaded: purpose first, then precondition, then the two outcome branches. The em-dash parenthetical and 'steering toward filling in the gaps' phrasing add slight verbiage, but nearly every clause carries actionable information.

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 no output schema, the description does the work of explaining return/outcome states — auto-approved versus unapproved draft — and the next call an agent can make. It stops short of describing what the generated guide itself contains or how to inspect it (get_brand_guide), which would round it out for a 1-param generation tool.

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 brandId parameter is already documented as coming from list_brands. The description restates the scan prerequisite, adding marginal context but no format or resolution detail beyond the schema. Baseline 3 applies when 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?

States a specific verb and resource ('Generates a brand guide') plus its input source ('from a brand's completed website scan'), which separates it from get_brand_guide, update_brand_guide, and regenerate_brand_guide_section. An agent can tell what is produced 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 precondition (create_brand's scan must have finished), spells out the auto-approval path and that generate_strategy can follow immediately with no approve_brand_guide click, and names the one case (thin scan) where the draft stays unapproved. This is when/when-not/alternatives in full.

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