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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description earns credit for adding content-level disclosure: what the brand sheet contains (projects, sender identities, audiences, guide index) and that both forms include the house writing style. It does not describe failure behavior when a name is not found, which keeps it below 5.

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 front-loaded sentences with zero filler: the two retrieval modes come first, the return content second, the safety boundary last. Every sentence carries information not already in structured fields.

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?

With no output schema, the description correctly compensates by enumerating the brand sheet's contents and the shared writing style. A single-parameter read tool is well covered; only the not-found / empty-guide case is left unstated.

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%, so the baseline is 3, but the description adds genuine semantics beyond the schema: omitting the parameter changes the resource returned entirely (brand sheet instead of a specific guide), which the schema only hints at with 'Omit to list identities and guides.'

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?

States a specific verb (retrieve) and two named resources (a saved design guide by name, or the workspace brand sheet), plus the precise condition that selects between them. An agent can distinguish this from list_pages/get_project style siblings 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 when-to-use for both modes (supply a name vs omit it) and explicitly rules out adjacent behavior: 'does not extract a website or modify records,' which steers the agent away from web-extraction siblings. It does not name a specific alternative tool, so it stops short of a 5.

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