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

The description goes well beyond the annotations by disclosing that this writes to Studio, creates billable AI usage, executes synchronously, supports validate_only/preview_only/execute modes, has a completed_items_not_rolled_back partial failure policy, returns internal application state, derives deterministic retry keys, and requires seatId/seatName on writes when multiple seats are authorized. These are substantive behavioral disclosures that annotations alone do not provide.

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 description is dense but mostly purposeful, front-loading the core purpose and then adding concise operational facts. It reads as a list of telegraphed policy statements, and while every sentence carries useful information, the paragraph format makes it slightly harder to parse. Minor redundancy around 'mutation' and 'seat' exists, but overall it is appropriately sized for the information conveyed.

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?

The tool is complex with 9 parameters, an output schema, and multiple behavioral policies, and the description covers most essential operational context: sync execution, billable usage, mutation modes, failure policy, idempotency, seat selection, and response handling. The main gaps are the lack of explicit sibling differentiation and the unexplained requestedSections and forceRefresh parameters, but the output schema and parameter names reduce the impact of those omissions.

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 0%, so the description carries the burden of explaining parameters. It meaningfully clarifies idempotencyKey semantics and the exact seatId/seatName requirement for mutations, but it leaves requestedSections and forceRefresh unexplained. Some parameters are self-explanatory from their names, but the description only partially compensates for the complete lack of schema parameter descriptions.

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 states a specific action ('Refresh and save') on a specific resource ('a standalone Studio advertiser brand profile'), making the tool's function clear. The write classification and 'standalone' qualifier help distinguish it from read-only siblings like get_brand_profile and from refresh_brand_visuals.

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?

The description provides operational constraints such as mutation modes, task support being forbidden, and seat requirements, but it never explains when to choose this tool over alternatives like get_brand_profile or refresh_brand_visuals. There is no explicit when-to-use or when-not-to-use guidance relative to sibling tools.

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