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

Annotations already provide readOnlyHint=true, so the safety profile is covered. The description adds valuable behavioral details: 'Deterministic. No LLM cost.' and enumerates the output types, providing context beyond the annotation without contradicting it.

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 description is compact and front-loaded. The first sentence states the purpose, the second enumerates deliverables, and the third adds a key behavioral note. Every sentence adds value with no 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?

Given the output schema exists, the description need not detail return formatting. It provides a clear deliverable list and behavioral notes. However, it could clarify how parameters influence the pack (e.g., market or medium variants), which would make it more complete for a complex 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 description coverage is 100%, so the schema fully documents all five parameters. The description does not add parameter-specific semantics beyond listing the outputs, which may implicitly depend on parameters like 'medium' or 'market', but this is not stated. Baseline 3 is appropriate.

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 explicitly states the tool's purpose: 'Complete brand asset pack' and lists the specific returned artifacts (CSS variables, Tailwind config, Figma tokens JSON, citation cards, Markdown brand guide). This clearly differentiates it from more specialized siblings like palette_export or palette_pdf.

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 phrase 'Everything a brand team needs to ship' implies this is the all-in-one export tool, but it does not explicitly name alternatives or state when not to use it. There are many sibling export tools, and the description offers no direct comparison or exclusion criteria.

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