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

Annotations declare destructiveHint=true and idempotentHint=false; the description adds that content is saved verbatim and is consumed as context by generate_strategy/generate_campaign, which explains downstream effects. It does not explicitly warn against duplicate creation being non-idempotent as a risk, but the 'instead of saving a duplicate' line covers the practical hazard. Minor gap: no mention of permanence/undo limits beyond wording 'permanent document'.

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?

Three sentences, front-loaded with the core action and effect, then routing guidance. Slightly dense with a parenthetical enumeration of content kinds, but every clause earns its place.

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 save-mutation tool with no output schema, the description covers what is stored, how it is used downstream, and when to use an alternative. It does not describe what the tool returns (e.g., an id), which would help the agent chain to update_research_brief, but the dashboard-URL fallback mitigates 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?

Schema coverage is 100%, so each parameter is already documented in the schema, including the 'domain' enum semantics. The description adds nothing about individual parameters beyond what the schema states, which is the expected baseline when 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?

States a specific verb (Saves) and resource (AI-synthesized research brief), and enumerates the content domains (market sizing, competitor analysis, audience/persona notes). It explicitly distinguishes itself from update_research_brief by naming that sibling and the condition that selects it.

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 when-to-use ('whenever a conversation produces real research worth keeping') and when-not (to revise an existing brief, use update_research_brief instead of saving a duplicate). It even tells the agent where to find the existing brief id.

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