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

Annotations flag destructiveHint=true, readOnlyHint=false, idempotentHint=false. The description adds meaningful context beyond them: it clarifies the regeneration source and that hand-edited briefs are never overwritten, which materially softens/qualifies the destructive profile. No contradiction with annotations.

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?

Purpose is front-loaded and the sentences earn their place, but the first sentence nests a large parenthetical defining the brief, making it dense. Slightly heavy but not wasteful.

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 one-param mutation tool with full annotations and no output schema, the definition covers trigger, source, and preservation behavior. Nothing essential is missing, though return/result handling is left unstated.

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?

Single parameter with 100% schema description coverage ('The brand's id, from list_brands'), so the schema already carries the semantics. The description adds nothing about the brandId parameter itself; baseline 3 applies for high 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?

States a specific verb (regenerates) and resource (the brand's knowledge brief), then defines what that brief contains and where it comes from (the approved guide). It is easily distinguishable from siblings like get_brand_brief and generate_brand_guide.

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 frames when to invoke it: 'Runs automatically on every guide approval; use this for an on-demand re-run.' That clearly positions the manual use case, though it does not name a sibling alternative to avoid.

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