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

Annotations already declare this is a safe, closed-world read, so the safety story is covered. The description adds non-obvious behavioral context beyond that: the writing rules are the client's instructions and are "binding on every article," telling the agent these constraints must be respected downstream. It does not say how the tool behaves when the brand is ambiguous or absent, which keeps it below a 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?

One sentence, front-loaded with what is returned, ending with the actionable directive to read it before drafting. Every clause names a distinct returned section; nothing is redundant 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 burden of describing return contents, and it does so by enumerating the profile fields, competitors, instructions, and Autopilot. Nothing essential for calling it correctly is missing; only details like response shape or how large the payload is remain 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?

There is a single optional parameter with 100% schema description coverage, including the note that it may be omitted for single-brand accounts. The description adds no information about the brand identifier, so this sits at the baseline where the schema does all the work.

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 enumerates exactly what the tool returns — brand profile fields (offer, category, language, markets, about, positioning, products), competitors, writing rules, and Autopilot — which clearly separates it from narrow siblings like get_competitors, list_brands, and update_brand_instructions. It lacks an explicit verb (it is a noun phrase), so it falls short of a 5, but the resource scope is unusually precise.

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?

"Read it before drafting or changing instructions" gives an explicit precondition tied to concrete sibling actions (draft_article, update_brand_instructions). It does not name negative cases or alternatives (e.g., use get_competitors if you only need the competitor list), so it stops short of full when/when-not guidance.

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