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

With no annotations, the description carries the full behavioral burden. It discloses the returned brand configuration, which is useful, but does not explicitly state that it is read-only, whether it requires shop access permissions, or what happens on invalid shop IDs.

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 efficient sentence, front-loads the core concept ('How this shop's quotes and invoices look'), and lists representative fields without wasted words.

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?

An output schema exists, so the description does not need to explain return structure; it still helpfully previews the kind of brand data returned. Input semantics and read-only behavior are less complete, but for a simple getter with one required parameter, the definition is largely sufficient.

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 schema has one required parameter, `shop_id`, with 0% description coverage. The description says 'this shop's' but does not explain the parameter, its UUID format, or how it identifies the shop, so it adds little 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 clearly identifies the specific resource being retrieved: the shop's quote and invoice branding, including accent color, license number, footer text, logo size, and Doing Work attribution. It is distinguishable from `shops_setBrand` by its descriptive/read-oriented framing, though it does not explicitly state a verb like 'get' or name the sibling.

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?

Usage is implied by the phrase 'How this shop's quotes and invoices look,' suggesting retrieval for inspection. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no mention of the related `shops_setBrand` alternative.

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