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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuine domain semantics beyond them: which content check_post enforces, that pending_rule_changes await a person, and the precedence of rules over playbook advice. It does not describe error behavior when a brand id is invalid, but the interpretive context is substantive.

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?

Every clause carries information with no filler, and the highest-value content (rules, then pending changes, then per-platform data) is front-loaded. But it is delivered as one sprawling run-on sentence with heavy parenthetical nesting, which is hard to parse and largely duplicates what the output schema already enumerates.

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?

Because an output schema exists, the description need not enumerate return fields, yet it supplies the interpretive layer the schema cannot: the rules-vs-guidelines distinction, machine-check status, and rule precedence over playbook advice. It omits when-to-call guidance and failure behavior, which are the remaining gaps.

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 description coverage is 100% and there is a single optional parameter, so the schema fully documents that brand is an id from get_workspace and is optional for single-brand workspaces. The description adds nothing about the parameter, 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?

The description makes clear this returns a brand's configuration: rules (with their fields), guidelines, pending rule changes, auto-approval state, and per-platform account/reach data. The verb 'get/retrieve' is implied rather than stated, and it never explicitly contrasts with get_workspace, but the resource and scope are 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?

Usage is implied (call it to inspect a brand's rules, guidelines, accounts and playbook) and it embeds useful interpretive guidance — rules are machine-checked by check_post while guidelines are not, and brand rules take precedence over the playbook. However, it never states when to use this versus get_workspace or how the optional brand parameter should be supplied.

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