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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description goes further by disclosing the aggregate behavior (deduped across every campaign), failure reporting with cause and next step, and the unusual consumer instruction 'Read `brief` to the user as-is' — genuinely useful context beyond structured data.

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 content is front-loaded with the payload description before the usage triggers, and nearly every clause carries distinct information. It is dense and slightly long, but not padded.

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 fully carries the burden of what comes back: sentence count, the four content categories, and the single link. An agent knows exactly what it will receive and how to present it.

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 100% and the single parameter already documents that brandId comes from list_brands. The description adds no parameter-level syntax or format detail, so the baseline 3 applies — the schema does the heavy lifting.

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 verb and resource ('brand-level check-in in one call') and precisely enumerates the content: pending owner actions deduped across campaigns, next-7-day schedule, last-7-day activations, failures with cause and next step, and one link. It distinguishes itself from siblings by noting it replaces calling list_campaigns + get_results_verdict per campaign.

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?

Explicit triggers are given ('how's it going', 'what do I need to do', 'what's happening this week') plus an explicit alternative it supersedes (list_campaigns + get_results_verdict). Nothing about when or when-not to use it is left to inference.

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