brand_deepen_identity

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

No annotations provided, so the description fully handles transparency. Describes that mode 'interview' returns questions, mode 'record' saves answers, and anti-patterns become enforceable rules in brand_preflight. No contradictory statements.

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, highly informative, no fluff. Front-loaded with the core purpose, then covers modes and usage context efficiently.

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 tool with two modes and six sections, the description provides adequate context: sequencing, return values, and integration with brand_preflight. No output schema, but mentions returns completion status, which is sufficient.

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 coverage is 100%, but description adds value by explaining the purpose of each mode and the sections. It clarifies that 'interview' returns structured questions for missing sections and 'record' writes to visual-identity.yaml.

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?

Clearly states the tool defines visual identity rules beyond colors/fonts, enumerating specific aspects (composition, patterns, etc.). Distinguishes from siblings like brand_extract_visual by focusing on the deepen step after Session 1.

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 'Use after Session 1 (core identity extracted).' Explains the two modes and their purposes. Does not mention when not to use, but the context is clear enough.

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