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

No annotations, so the description carries the full burden. It discloses that the operation is paid (implying cost/auth), currently synchronous despite poll existing, and that GET is discovery only. It does not specify the payment/authorization mechanism beyond what the schema's authorization field says, nor what the sync call returns or how long it takes.

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 terse clauses with no filler, front-loaded with what the tool is. Slightly telegraphic, but every fragment carries information relevant to invocation.

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 an 11-parameter paid generation tool with no annotations and no output schema, the description is thin. It omits return shape, sync latency expectations, the payment flow, and how the two input modes differ in output, leaving the agent under-informed on a costly operation.

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 only 18%, so the description should compensate, and it does state the required parameters and the anyOf input modes. But it doesn't explain count clamping, the distinction between product and brief, or the authorization parameter's real role in payment.

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 deliverable: a paid Hero headline + subheadline generation pass, distinguishing it from the poll sibling. The phrase 'Separate paid Hero' implies this is distinct from a free tier, which adds useful scope. However it doesn't fully define what the 'Hero' section is for an unfamiliar agent.

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?

It gives input requirements ('Requires brand_name, audience, and brief or all five structured fields') and notes GET is discovery only, which implies this is the POST/generation path. But it never says when to use this versus poll, or 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.