Start Article Writer Pipeline

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

Discloses immediate return with jobId, ~5s claim time, default section, credit usage. Schema adds force behavior. No annotations exist so description carries full burden, and it does well.

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?

Four sentences, front-loaded with key action, no filler. Efficient and clear.

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?

Covers enqueue action, return type, timing, default, credits, and references sibling for polling. Lacks error handling details but sufficient for a simple tool with clear sibling.

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 covers 100% parameters with descriptions. Description adds minimal value: default section elaboration. 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?

Clearly states the action (enqueue a writer-pipeline job) and resource (existing WriterSession). Distinguishes from sibling get_writer_pipeline_status by describing the polling pattern.

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 explicit context: requires existing WriterSession, default section, and references sibling for polling. Schema description adds prerequisite (create session via web UI). No explicit exclusion for concurrent jobs, but force parameter is described.

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