basecoat_creative_director

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds useful context that this is a read-only advisory stage in a multi-stage pipeline, but discloses nothing further about what it returns or any limits.

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?

Two sentences, stage tag front-loaded, no padding. It is efficient, though the topic enumeration largely duplicates the topic enum and could be trimmed.

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?

With 100% schema coverage and full annotations, the structured data covers inputs and safety, and there is no output schema to explain. What remains missing is disambiguation from the crowded sibling set (get_rhythm_rules, get_design_rules, basecoat_page_architect), which an agent in this pipeline genuinely needs.

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% with 8 well-documented parameters and five enums, so the schema carries parameter meaning entirely. The description's topic list loosely echoes the topic enum but adds no syntax, defaults, or interaction semantics beyond what the schema already provides; 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 states it surfaces Kanso minimalism and design intelligence across enumerated topics (typography ladders, spacing rhythm, whitespace density, contrast ratios, style packs, elevation), which aligns with the topic enum. However, the verb 'Surface' is abstract and the phrasing is marketing-flavored rather than a concrete verb+resource. It does not distinguish itself from close siblings like get_rhythm_rules, get_design_rules, or get_creative_direction.

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 '[STAGE 2: RULES & RHYTHM]' tag plus 'Next step: Call basecoat_compose_stack or basecoat_component_syntax' gives genuine workflow positioning. But it never states when to choose this tool over alternatives such as get_rhythm_rules or get_design_rules, so usage is only implied by pipeline order.

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