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

readOnlyHint=true already covers the safety profile, so the description earns credit for added context: it discloses the bundled payload (brand kits, critics, presigned thumbnails, decision log) and that the critics are a machine-checkable standard enforced by Director gates and score_composition. 'Presigned thumbnails' usefully signals links may be ephemeral, though no auth or rate-limit detail is given.

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 sentences, front-loaded with the returned contents and closing with the usage trigger. The 'legible taste' / 'house style' metaphors add flavor without much payload, keeping it just short of maximally efficient.

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 return values need not be re-explained, and a zero-param read tool requires little more. The description covers purpose, payload, and the pre-compose usage condition adequately; only minor behavioral detail (auth, link lifetime) is absent.

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 takes zero parameters, so per the baseline there is nothing for the description to add here. It correctly describes an implicit org scope with no parameter-level gaps.

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 states a specific resource (the org's profile) and enumerates exactly what comes back: brand kits, critics, reference media, and a checkpoint-decision log. It is distinguishable from neighbors like get_account or get_brief, though the 'legible taste in ONE read' framing is flowery and only clarified by the enumeration that follows.

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?

Gives an explicit when-to-use trigger: 'Read this BEFORE composing for an org you haven't worked with.' It does not name an alternative tool or when NOT to use it, but the precondition is clear and actionable.

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