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

Annotation Contradiction: annotations mark destructiveHint=true, but the description explicitly says 'Proposes only — never saves anything' and describes accepted items being applied later via update_brand_guidelines. This directly contradicts the structured annotation. The description otherwise discloses approval behavior and empty-material behavior, but the contradiction to destructiveHint forces a score of 1.

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 main description is front-loaded with the core workflow and quickly clarifies propose-only behavior and the update_brand_guidelines handoff. The bracket-sensitive approval block adds necessary usage guidance, though it is dense and slightly dense enough to keep from a 5, it still earns a strong score.

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 no output schema, the description compensates by describing return expectations: proposed brand guide items, verified receipts with quotes and source docs, and the empty result when no source material exists. It also covers the acceptance workflow and approval path, so nothing needed for correct invocation is missing.

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 single parameter companyId already has a complete schema description and the schema coverage is 100%, so the description does not need to add much parameter-level meaning. The description's references to 'company's own canon documents' reinforce the target-company context but do not materially exceed the schema's coverage.

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 a specific action and resource: drafting a first brand guide extracted from the company's own canon documents, with verified receipts. It distinguishes itself from read-only brand-guideline tools and names update_brand_guidelines as the follow-up tool, making the tool's role unmistakable.

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 explicit when-to-use conditions: when the user accepts an offer to build a brand guide from existing material, or explicitly asks to assemble one. It also states the negative case, telling the agent to ask instead when no material exists, and gives operational guidance around sensitive-tier approval.

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