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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds value by disclosing what payload the read returns, but says nothing about permissions, freshness, or whether the context may be absent for accounts without one.

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?

One sentence plus a short imperative, no filler. However the main clause is a long colon-delimited inventory and the actual action ("read") only appears in the trailing sentence, so it is not optimally front-loaded.

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 read-only, single-optional-parameter tool with no output schema, enumerating the returned content is the right level of detail and no return-value documentation is needed. A note on what happens when no business context exists would complete it.

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 single project parameter already documents "id or exact name" plus the optional-when-single-project rule. The description adds no additional parameter meaning, so 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?

It names the resource specifically and enumerates what the context holds (design language, aesthetics, motifs, colours, type, imagery, avoid-list, provenance), which is far beyond a restatement of the name. It never distinguishes itself from similar siblings like get_brand, get_overview, owner_facts_read or voices_read, so an agent cannot tell from this text alone which of those overlaps.

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?

"Read it before changing it" gives an implied ordering (fetch before mutating) but names no alternative tool, no conditions for skipping, and no exclusions. An agent can guess the read-before-write use case but gets nothing about when to pick this over get_brand.

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