brand_build_themes

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

With no annotations, description discloses key behaviors: auto-generates IDs for record mode, returns theme data and balance analysis, and states typical brand needs (3-5 themes). Could mention authentication requirements or mutation effects.

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?

Concise paragraph front-loads purpose, then efficiently breaks down modes, typical usage, and return values. Every sentence adds value with no redundancy.

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, description adequately explains return value (theme data and balance analysis) and covers all modes. Provides strategic guidance on theme count and intent balance, making it self-contained.

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 descriptions already cover 3 parameters. Description adds value by explaining mode behaviors, how answers relate to recording, and that theme_id is optional for new themes. Provides context beyond schema.

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?

Description clearly states the tool defines editorial content themes as strategic pillars. It differentiates from siblings by focusing specifically on theme building, with no overlap suggested.

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 explains each mode and their intended use (interview for guidance, record for saving, list for overview). Does not directly compare to sibling tools but provides clear context for when to invoke.

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