Complete Brand Colour Intelligence Report

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

Annotations already indicate readOnlyHint=true. The description adds valuable behavioral context: 'runs entirely internally -- no chained calls, cannot be blocked by agent safety filters' and mentions 'Two Claude calls total'. This goes beyond annotations, though it could detail what 'internal' means.

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 dense sentences cover purpose, inputs, outputs, usage guidance, and behavioral details. Front-loaded with 'one-call complete'. No unnecessary words.

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 complexity (7 params, nested objects, many siblings, output schema exists), the description covers purpose, usage, safety, and output list comprehensively. Could mention that output schema is defined separately.

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 baseline is 3. The description lists input parameters but does not add new semantics beyond the schema. However, it lists output components which indirectly contextualize inputs.

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 clearly states 'one-call complete brand colour intelligence report' and lists both inputs and outputs. It explicitly distinguishes itself from sibling tools like colour_strategy, cliche_breaker, etc., by saying 'use this instead of chaining...'.

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 description explicitly tells when to use the tool (instead of chaining multiple individual tools) and provides a clear context. It does not give explicit when-not-to-use scenarios, but the alternative is implied.

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