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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds useful behavioral context: it returns the same data as get_brand_context but in raw JSON, and notes that get_brand_context additionally includes saved facts and assets. It doesn't cover rate limits or pagination, but for a read-only getter this is strong added value.

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 with zero waste. The main purpose and distinguishing detail come first, followed by the routing guidance to the alternative tool.

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?

There is no output schema, so the description must convey return value information. It does so by stating that the tool returns the same brand identity, voice, and visual data as get_brand_context, with examples like hex colour and tone attributes. This is adequate for an agent to decide whether to call it, though a more explicit list of returned fields would make it fully complete.

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?

The input schema has 100% description coverage for the single 'brand' parameter, including guidance to ask the user if unclear. The description does not add any meaning about the parameter beyond what the schema already provides, so the baseline score 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 states a specific verb ("Returns") and resource ("brand identity, voice and visual data"), and explicitly distinguishes the tool from its sibling get_brand_context by noting it returns raw JSON fields for programmatic use. An agent can immediately understand what this tool does and how it differs.

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?

It gives explicit guidance on when to use this tool (programmatic use, e.g., reading a hex colour or tone attributes) and when to prefer the alternative ("Prefer get_brand_context for any writing task"). Both the positive and negative conditions are clearly stated.

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