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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral details: URL normalization behavior ('www.example.com' → 'example_com.json') and the requirement that the brand kit exists. These go beyond the annotations and inform the agent about input handling and preconditions.

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 structured with clear sections (USE FOR, RETURNS) and is front-loaded with the purpose. It's not overly verbose; each section adds value. The main purpose is stated first, followed by useful details.

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 tool with one parameter, the description covers the purpose, return fields, prerequisites, and input normalization. It lacks explicit error handling or missing-brand behavior, but given the simplicity and the presence of annotations, it is sufficiently 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?

Schema coverage is 100% with a well-described `domain` parameter including examples. The description adds the normalization behavior (accepts URLs with/without protocol, converts to domain) which is not in the schema, enhancing understanding of how the parameter is processed.

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 the verb 'Retrieve' and the resource 'brand kit configuration', making the core action explicit. The 'USE FOR' section enumerates specific use cases (check stored info, review colors/fonts/logos before updating, verify existence) which distinguish it from siblings like generate_brand_kit and update_brand_kit.

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 provides explicit use cases and notes the prerequisite that a brand kit must exist, implying when to use this tool vs. generate_brand_kit. However, it doesn't explicitly name alternatives or state exclusions (e.g., when not to use), so it's clear but not fully explicit about routing.

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