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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavior: omit brand_id to list all summaries vs. pass it to get full profile, and it specifies the return fields (full profile JSON, schema_version, timestamps, brand_kit_sync_status). This goes beyond the structured annotations.

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 compact paragraphs: the first condenses purpose and use cases, the second covers parameter modes and return details. Every sentence earns its place; no redundancy or filler.

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?

With no output schema, the description compensates by specifying the return payload and its fields. It also covers both operational modes (get vs list) and the purpose context. For a simple read-only tool, this is complete and well-rounded.

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% coverage with 'Omit to list all.' The description adds value by clarifying the output differences: listing returns summaries of (brand_id, updated_at), while reading one returns the full profile JSON with additional metadata. This enriches the parameter's meaning beyond the schema.

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 'Read back the persisted brand profile without modifying it'—a specific verb, resource, and non-mutating scope. It distinguishes itself from the sibling 'set' tool by framing a use case as 'inspect the current shape before a partial update.'

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 three explicit usage contexts: confirm a profile landed, check the active profile, or inspect before a partial update. It doesn't explicitly name alternative tools or state when not to use it, but the read-only framing and update context imply the boundary.

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