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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered and the description does not need to restate it. The description adds that the profile is workspace-scoped and enumerates the returned fields, but says nothing about the case where no profile has been saved — an agent cannot tell whether this returns an empty object or errors.

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?

Two short sentences: the first front-loads what is returned, the second gives the actionable reason to call it. No filler, no repetition of the title, and the field list doubles as a preview of the response.

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 parameters and no output schema, the description carries the burden of describing the return value, and it does so by listing the profile's fields. The one gap is behavior when the profile is unset or partially filled, which matters for a planning gate like this.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning for the description to add. Nothing in the text misdescribes the calling signature.

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 the resource (the workspace's saved brand profile) and enumerates its contents — category, channels, languages, markets, preferred model — so an agent can tell it apart from get_ad, list_ads, or get_credit_balance. It is a noun phrase with the verb supplied only by the title, which keeps it just short of a textbook verb+resource statement.

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 gives an explicit trigger: read this before proposing an ad so the suggestion reflects what the workspace actually sells, which effectively routes the agent to call it ahead of draft_ad_plan or generate_ad_script. It stops short of any when-not guidance (e.g., that it is unnecessary during pure reporting/stats calls).

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