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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations by mandating call ordering and warning against guessing brand colors. It does not invent behavior that conflicts with annotations.

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 front-loaded with the resource and content list, then gives routing guidance. The line 'If you skip this, the brand page might as well not exist' is rhetorical and not strictly necessary, but it is short and the rest is information-dense.

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 simple read-only retrieval tool with one well-documented parameter and no output schema, the description provides all needed context: what data is returned, when to call it, and how it relates to other tools. An agent can correctly select and invoke this tool without further elaboration.

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% and the single parameter companyId is already documented in the schema. The description does not add parameter-level details, but given full schema coverage, the baseline of 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 specifically identifies the resource ('company's brand guidelines') and enumerates its content areas (name, tagline, colors, typography, tone, naming rules, dos/donts). It also distinguishes itself from get_voice_profile by clarifying that this tool covers how the brand LOOKS and stands for, while voice profile covers HOW to write. This makes sibling differentiation immediate and concrete.

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 gives explicit routing instructions: call before any operator-facing artifact and before generate_image_xai, and never guess brand colors. It also names the complementary tool (get_voice_profile) for writing voice. This leaves little ambiguity about when to use this tool versus alternatives.

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