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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write-safe profile is covered. The description goes beyond by characterizing the action's weight ('Same trust level as clicking Approve in the Rebbel dashboard'), which is valuable non-redundant context for an irreversible-looking sign-off, though it doesn't discuss whether approval can be reverted.

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 purpose, then necessity, then trust-level caveat — a logical progression. Slightly dense with three clauses in one sentence, but no filler sentences.

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 2-param mutation tool with full schema coverage and annotations covering safety, the description supplies the missing decision context (when approval is needed, trust level). No output schema exists, so return values needn't be explained; only minor gap is reversibility.

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 description coverage is 100% and both params (brandId, guideId) are described in the schema with their provenance (list_brands, get_brand_guide). The description adds no parameter-level detail, so the baseline 3 applies.

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 ('Approves') and resource ('draft brand guide') and clarifies scope: the human sign-off required before a guide can drive strategy or campaign. This clearly distinguishes it from sibling approve_* tools (approve_copy, approve_post, approve_strategy).

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?

Explicitly says when it's needed ('Only needed when generate_brand_guide didn't already auto-approve it, which happens on a thin/low-confidence website scan') and includes a strong when-not caveat: 'only call this once you (the user) actually want it approved.' This is precisely the alternative/condition guidance a 5 requires.

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