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

Goes well beyond annotations: it discloses that scope 'everything' rewrites description, audience, voice and products and replaces user edits, that it runs in the background, that scope 'look' preserves an uploaded logo, that the call takes about a minute, and that it is free but requires an active plan. This is exactly the context the readOnlyHint=false / destructiveHint=false annotations cannot convey.

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 the core action and the default scope, then the riskier mode. It is dense with nested parentheticals, which slightly hampers scanning, but every clause carries operational information and nothing is 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 long-running, partly background, partly destructive operation with no output schema, the description covers duration, result delivery ('answers with the updated brand when done'), the async polling step, the free/plan constraint, and the confirmation requirement. An agent has everything needed to call it correctly and not surprise the user.

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 67%, but the description fully compensates: it defines what each enum value of scope actually does, explains the logo-preservation side effect, and states that confirm is required only for scope 'everything' after user agreement. That is meaning well beyond the schema's terse field descriptions.

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 ('Reads the brand's website again') plus the trigger scenario ('after a rebrand'). It then splits the tool into its two modes and names the siblings it is not (update_brand, get_brand), so an agent can distinguish it from neighbors 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?

Explicit routing: scope 'look' for visual-only refresh, scope 'everything' for full re-analysis, and 'To set a field to a value you already know, use update_brand instead.' It also states the precondition for confirm: true (user agreement) and the follow-up step (read get_brand a few minutes later).

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