content_brief_outline

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

No annotations are provided, so the description carries the full burden. It does disclose the content of the generated artifact, which is meaningful behavioral context given there is no output schema. However, it says nothing about determinism, cost/latency, permissions, or whether related_keywords changes the output shape.

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?

A single front-loaded sentence with no filler, and the parenthetical list of outputs is information-dense rather than padding. Slightly heavy nesting, but every element 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?

The output enumeration usefully compensates for the missing output schema, and no safety annotations are needed for a generation tool. But with 0% parameter coverage and no usage routing against four siblings, the definition is only minimally adequate.

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 must compensate for all four parameters. It only accounts for keyword and related_keywords (and marks the latter optional); audience and word_count are never mentioned, and word_count's 300-10000 bounds go unexplained.

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 ("Generate") and resource ("content brief") and enumerates the concrete deliverables (intent, title options, meta draft, H2 outline, questions, on-page checklist). This clearly separates it from narrower siblings like check_title_meta or classify_search_intent, though it never names them explicitly.

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 only scoping cue is "for a target keyword plus optional related keywords," which is parameter guidance rather than when-to-use guidance. There is no statement of when this tool is preferred over classify_search_intent (whose intent output overlaps) or the other siblings, and no prerequisites or exclusions.

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