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

With no annotations, the description carries the full behavioral burden but doesn't disclose critical traits: whether generation is synchronous or returns a job id (siblings like get_job_status and trigger_scan suggest async workflows), what permissions are required, whether existing drafts are overwritten, or whether it incurs cost/rate limits. It only clarifies that outputs are draft articles, leaving the mutation/async profile undisclosed.

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 that identifies the action and resource without waste. The parenthetical about pipeline_type is slightly cryptic but adds relevant domain context rather than padding.

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?

For a two-required-parameter generation tool with no annotations and no output schema, the description should explain what gets returned (job id vs. draft ids) and the async semantics implied by sibling job-status tools. It also leaves opportunity_ids undocumented, so an agent lacks enough context to call it correctly and interpret the result.

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 50%: product_id is documented in the schema, but opportunity_ids has no schema description. The description partially compensates by framing these as 'selected opportunities,' implying an array of opportunity ids from a prior listing. It also introduces pipeline_type context (seo_intent or reward_intent) that explains how the product determines draft type, but doesn't map this clearly to any parameter.

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 and resource: 'Generate draft articles for selected opportunities.' This clearly distinguishes it from siblings like list_drafts and publish_content. However, it doesn't explicitly name which sibling to use for follow-up steps (e.g., get_job_status), leaving some differentiation implicit.

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 implies usage context—generating drafts for opportunities selected from a prior listing step—but offers no explicit when-to-use/when-not guidance or alternatives. An agent must infer that this is a write operation to be used after list_opportunities and before publish_content, without being told so.

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