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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond that: the results are limited to kits 'available to the user' and it states exactly what is returned (brand_kit_id, name, thumbnail). It does not discuss pagination, but the continuation parameter schema covers that.

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?

Five short, purposeful sentences. The core action is front-loaded, the domain definition earns its place, the exclusion is relevant, and the return shape is stated without redundancy.

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?

Despite having no output schema, the description names the returned fields. The tool is low-complexity, annotations cover the read-only/destructive profile, the sibling distinction is clear, and the input schema handles parameter semantics. Nothing essential is missing for correct invocation.

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%, so the baseline is 3. The tool description does not add parameter-level detail, but it doesn't need to because the schema already explains limit, user_intent, continuation, and resolve_icon_thumbnails clearly.

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 opens with a specific verb and resource: 'Find or browse the Canva Brand Kits available to the user.' It clearly defines what a Brand Kit is and explicitly contrasts with Brand Templates, so an agent can distinguish it from search-brand-templates and other siblings.

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 concrete reasons to use the tool: find a user's brand identity, check team brand elements, or identify the needed Brand Kit. It also provides an explicit exclusion ('Not for finding individual Brand Templates'), which semantically routes the agent toward the sibling search-brand-templates tool.

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