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

The description says 'no external research or outbound actions' while annotations set openWorldHint=true, which typically indicates the tool may interact with the external world. This is a direct contradiction. While it adds useful context about payment and review, the contradiction warrants a score of 1.

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, zero filler. The first sentence states the core function, the second scopes inputs and outputs, the third states price and authorization. All content 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 description covers the core behavior and payment requirement, but given the tool has five parameters, a nested input object, no output schema, and a contradictory annotation, it's incomplete. The agent cannot infer correct values for idempotency_key, result_expires, or the structure of the 'brief' field. The openWorldHint contradiction further reduces trust.

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 explain parameters but doesn't. It mentions 'audience' as an output component but not as an input parameter; it doesn't explain 'brief', 'source_text', 'result_expires', 'idempotency_key', 'result_signature', or 'payment_signature' semantics. The only hint is that payment requires wallet authorization, which loosely relates to payment_signature, but that's insufficient.

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 'Produce' and resource 'writing brief' with explicit components (audience, thesis, outline, evidence, acceptance criteria), clearly distinguishing it from blog_draft which would produce the article itself. However, it doesn't explicitly name sibling alternatives like seo_content_brief, so it's not a perfect 5.

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?

Describes clear context: uses buyer-supplied information only, no external research, returns draft for human review, and requires explicit wallet authorization. This implies when to use it (for planning from existing info) but doesn't explicitly contrast with sibling tools or state when not to use it.

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