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

Annotations include readOnlyHint=true, so the description doesn't need to state safety. The description adds no behavioral detail beyond the annotation, but the annotation already covers the key trait. No contradiction.

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 a single short phrase, front-loaded and free of fluff. It is concise, though it could add a bit more context without becoming verbose.

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 tool with one parameter and a readOnlyHint annotation, the description is adequate. It doesn't explain return format, but no output schema exists and the tool is simple enough that an agent can infer the return from the resource type.

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%: the only parameter brand_kit_id is described as 'A brand_kit_id from list_brand_kits.' The description adds no additional parameter meaning, but the schema already provides sufficient guidance.

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 'Get brand kit' clearly states a specific verb and resource, and the title 'Get brand kit' reinforces it. It distinguishes from siblings like list_brand_kits and create_brand_kit, though it doesn't explicitly name them.

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 implies usage: call this to retrieve a single brand kit by ID. It doesn't explicitly state when to use this vs list_brand_kits or update_brand_kit, but the verb 'get' and the parameter description referencing list_brand_kits provide some context.

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