post_brief

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

No annotations are provided, so the description carries the burden. It discloses the tool produces a brief and rules, and explains the expected workflow. It doesn't mention side effects or limitations, but for a content-generation tool this is adequately transparent.

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 description is succinct and front-loaded with the core purpose. The archetype list and workflow instruction are directly useful, with no filler.

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 tool is simple: two parameters, no output schema. The description tells the agent what to expect (structure + rules), how to use the output, and what to do next. Given the tool's simplicity, this is fully complete.

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 0%, so the description must add meaning. It explicitly lists the allowed archetype values (build_in_public, lesson, teardown, opinion, result), adding significant value. The topic parameter is only implied via 'on a topic,' but its meaning is self-evident.

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 clearly states it returns a structured brief and rules for writing a post. The verb 'get' and resource 'brief' are specific, and it distinguishes itself from sibling publish tools by explicitly directing the agent to follow with publish_now or schedule_post.

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?

Provides clear usage context: use this first to prepare content, then publish. It explicitly names subsequent tools (publish_now, schedule_post) but doesn't give exclusions or alternatives for different scenarios, limiting a perfect score.

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