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

Annotations already mark readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds context beyond annotations: exact return content, the '0 credits' cost note, and the behavioral implication of hasBrand on downstream operations. While it doesn't detail error cases or latency, it enriches the behavior understanding meaningfully.

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?

Three sentences, each with high information density: first defines the resource, second gives usage decision logic, third excludes a common misconception. No filler, front-loaded with the core definition, and compact despite rich context.

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 zero-parameter read-only tool with no output schema, the description covers all essentials: what it returns, when to call, when not to call, the hasBrand flag's role, and the alternative path. An agent has everything needed to decide and invoke correctly without missing information.

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 tool has zero parameters, and the schema reflects that with 100% coverage (empty properties). Per the rubric, a baseline of 4 applies for 0 params. The description doesn't need to explain parameters and instead clarifies the output, which is appropriate.

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 states the verb (get) and resource (saved brand profile including products, logos, palette, positioning, and learned memory). It distinguishes itself from siblings like list_brands by specifying it retrieves the account/workspace's own brand, not a list. The purpose is unambiguous.

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?

Explicitly says 'Call it when you need to know whether a brand is on file' and provides conditional guidance (if hasBrand true/false), plus names the alternative draft_brand for onboarding. Also states when not needed ('Not a required first step before a render'), giving clear when-to-use and when-not-to-use instructions.

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