brand_status

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

With no annotations provided, the description fully bears the transparency burden. It clearly states it returns structured status data, describes the content (colors, fonts, logo, confidence, completion), and explains the fallback behavior (getting-started guide). No contradictions or omissions.

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 efficiently concise with four sentences, front-loading the main purpose. Every sentence adds unique value: what it shows, when to use, fallback behavior, and output nature.

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 parameters and no output schema, the description comprehensively covers what the tool does, its outputs, and its edge case (no .brand/). It is complete for effective agent usage.

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?

No parameters exist (schema is empty), so baseline is 4. The description adds value by explaining the tool's behavior and output without needing parameters.

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 uses a specific verb ('Check') and resource ('brand system progress'), lists what it shows (colors, fonts, logo, confidence, session completion, next steps), and distinguishes from sibling tools by focusing on overall progress and next steps rather than specific audits.

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 states when to use: resuming session, checking readiness, user asking 'what's the state of my brand?'. Also describes fallback behavior when no .brand/ exists, providing clear context for tool selection.

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