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

Annotations already cover safety (readOnlyHint, destructiveHint=false), so the description adds genuinely new behavioral context: the default scoping behavior, the fact that results are workspace-bound, and the important pitfall that brands are not unique by domain (www duplicates, empty copies) with only one holding data. None of this is derivable from the annotations or schema.

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?

Purpose and scope are front-loaded in the first clause, and each subsequent sentence carries actionable content (routing, duplicate handling, verification). It is dense and slightly long for a two-parameter list tool, but there is little filler.

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 list with no output schema, the description covers scoping, ownership, cross-tool routing, and data-ambiguity pitfalls well. It stops short of describing the shape of returned records (e.g., that entries carry site_id/domain/org_id), which is the only material gap given no output schema exists.

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%, so the schema already documents limit and org_id fully, making 3 the baseline. The description reinforces org_id's provenance ('from list_workspaces', omit for own workspace) but adds no format or constraint detail 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?

StartsWith a concrete verb and resource plus explicit scope: 'List the brands in ONE workspace'. It clarifies the default (own workspace, not every reachable brand) and distinguishes itself from list_workspaces, which it names. An agent can identify the operation and its boundary without opening the schema.

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 explicit routing: if a given brand is missing, call list_workspaces first, then re-invoke with that org_id. It also states an exclusion/verification rule — never pick a brand by domain name alone, confirm with synced_queries or use the provided site_id. This is precisely the when/when-not/alternative guidance the rubric reserves top marks for.

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