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

Annotations already declare readOnly/idempotent/safe, so the bar is lower. The description adds real behavioral context beyond them: the precedence rules that produce `effective` (explicit beats accepted suggestion, newest explicit wins, forbidden words accumulate) and provenance tracking per rule.

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?

The core content is front-loaded in the opening clause, and the exclusion note is placed last where it belongs. It is dense and slightly run-on with em-dash chains, but nearly every clause carries distinct information rather than padding.

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 carries the full burden of explaining returns and does so thoroughly: it enumerates returned rule categories, explains the `effective` resolution field, and notes provenance. Nothing essential for correct use is missing.

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 0% and there is one parameter (workspaceId) with no description in either the schema or the description. The field is largely self-evident, but with zero schema coverage the description does nothing to compensate, so it sits at the minimum-viable baseline.

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 names a specific resource (the lasting rules/brand memory) and enumerates its contents (audience, tone, CTA, visual direction, forbidden words, etc.). It explicitly distinguishes itself from operational facts and from get_brand_profile, so an agent can identify it 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?

It clearly routes the agent: operational facts (services, prices, links, accounts) live elsewhere and the `speaker` concept is in get_brand_profile. This gives strong context, but it never states an explicit 'call this when you need X' trigger or exclusions for the memory tool itself.

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