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

Adds substantial behavior beyond the annotations: partial-update semantics, logo constraints (public https, PNG/JPEG/WebP/SVG, ≤5MB), and the full lifecycle of clearFeedStyle including that cleared style is relearned on next 'My feed'/Refresh. The user-confirmation requirement is also disclosed.

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?

Front-loaded with the core behavior in the first sentence and the rest ordered by field importance; nearly every clause adds actionable detail. It is a dense single block, though, and would scan better as bullets.

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?

For a 15-parameter mutation with no output schema, the description covers the risky and ambiguous fields plus the upload workflow and feed-style consequence. Remaining gaps (exact semantics of keyProducts replacement, priceOffer null-clearing) are already covered by schema descriptions.

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?

With only 27% schema coverage across 15 params, the description carries most of the burden and does so for the non-obvious ones: colorPalette 'name:#hex' format, typography intent and case-dropping rule, logoUrl sources, clearFeedStyle booleans. Several fields (name, industry, description, targetAudience, mood, visualElements) are only named, not explained, keeping it short of a 5.

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?

Opens with a specific verb+resource ('Changes the brand profile') and immediately frames the patch semantics, so it is distinguishable from get_brand. It doesn't explicitly name the read counterpart as an alternative, which keeps it from a 5.

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 solid when-to-use context ('for a rebrand or a correction', 'pass only the fields to change') and routes logo file uploads to create_upload_link + get_upload. It also instructs asking the user before calling. No explicit when-not-to-use/exclusion against siblings beyond the upload path.

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