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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds valuable behavioral context: the operation is async, costs $9/1 unit, is research-grounded and quality-gated, and returns a payment_required payload when balance is empty. It also clarifies the cost model ('FREE - reads your connected/stored data, no AI credits'), which is a meaningful behavioral disclosure beyond the annotations.

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 information-dense but well-organized: it front-loads the core action and cost, then explains the async flow and error handling. It's slightly long but every sentence earns its place—the payment_required handling and async polling instructions are critical for correct usage.

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 essential workflow (async generation, polling, payment failure handling) and the output format (markdown + HTML). It doesn't detail the output schema's contents, but the output schema exists and the description doesn't need to explain return values. The only minor gap is not specifying what happens if the topic is invalid or if generation fails for non-payment reasons, but the core usage is well covered.

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 100%, so the schema already documents both parameters. The description adds context about the topic being a keyword/topic for SEO, but doesn't add new parameter-level meaning beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb ('Write'), a specific resource ('one in-depth SEO article'), and the delivery format ('markdown + HTML'). It also distinguishes itself from siblings by naming get_article as the polling mechanism and mentioning the payment_required payload, which clearly separates it from other tools in the list.

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 description explicitly explains the async workflow: call this tool, receive an article_id, then poll with get_article. It also gives clear guidance on how to handle the payment_required response (relay price and link, don't treat as failure), which is essential for correct agent behavior.

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