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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds a genuinely new behavioral fact not present in the schema or annotations: the required `templates:read` scope, i.e. auth requirements. It stops short of describing pagination or result limits, keeping it below a 5.

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 short, front-loaded lines: the operation and result contents come first, the scope constraint last. The parenthetical enumeration of profile fields partially duplicates what the output schema already conveys, which is the only wasted weight.

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?

The tool is simple (one optional param, rich annotations, output schema present), and the description covers purpose, contents, filter, and required scope. Missing are any note about result volume/pagination and any referral to `brand_kits_get`, the main thing an agent could get wrong here.

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% and the `name` parameter is already documented as a case-insensitive display-name filter, so the schema does the heavy lifting. The description only restates that the filter is optional, adding no format or matching details beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('List Brand Kit profiles') and even enumerates what a profile contains (voice, colors, pinned `/img/{id}` graphics, core pages), which lets an agent know what it gets back. It is distinguishable from `brand_kits_get` by the plural 'List', but it never explicitly says the sibling pair works as list-vs-single-fetch.

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 'Optional `name` filter' line implies the tool can be used either to enumerate all kits or to narrow to one by name. However, no explicit when-to-use guidance is given, and it does not route the agent to `brand_kits_get` when a single kit is needed.

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