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

Beyond the readOnly/idempotent annotations, it discloses that avoidThemes is a hard filter on everything Blawgy proposes, that each list entry records who added it, and that the result is null before a brief exists. With no output schema, this return-shape and null-state context is genuinely additive.

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 core resource description is front-loaded and dense with no filler, and the alternative-tool pointers close it out. The long enumerated middle sentence is information-rich but slightly heavy to scan.

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 single-parameter read tool with no output schema, the description fully covers what is returned, the null state, how to create or edit the brief, and that the call is free. Nothing an agent needs to call it correctly is missing.

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?

Only one parameter and schema coverage is 100%, so the schema already documents 'site' fully. The description adds nothing about the parameter itself, so the baseline 3 applies.

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 resource (the research brief) and enumerates exactly what it contains (business summary, audience, seedTopics, chaseThemes, avoidThemes, competitors, product core), which lets an agent distinguish it from get_refresh_brief, get_research_run, and get_research_status without opening any schema.

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?

Explicitly routes the agent to alternatives: 'Null when no brief exists yet (regenerate_research_brief creates one)' and 'Edit with update_research_brief.' It also flags cost ('Free.'), so the when-to-use and when-to-use-something-else decisions are both covered.

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