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

Beyond the annotations it discloses billing behavior ("Charged once"), the async execution model ("Poll the returned op; its result holds the issueId"), and a downstream approval gate before sending. That is exactly the context an agent needs for an expensive, open-world mutation, and none of it is repeated from the annotation block.

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 short sentences, each carrying distinct information: precondition, cost/idempotency, polling destination, and approval requirement. The action is front-loaded and there is no filler.

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?

With no output schema, the description correctly supplies the result path (op → issueId) and the surrounding workflow. It stops short of naming the polling tool or describing the op's shape, but the essential calling contract is 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 all four parameters are already documented, including the clientRequestId retry contract. The description only reinforces the quote provenance for credits/pricingVersion and adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and scope: draft one newsletter issue, gated on the owner having seen the quote. That plus the credits/pricingVersion params makes it distinguishable from soclo_newsletter_draft_quote and soclo_newsletter_issue_create, though it never names those siblings explicitly.

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 states a concrete precondition ("after the owner has seen the quote") and a retry rule ("reuse clientRequestId on a retry"), which tells the agent when it is safe to call and how to recover. It does not explicitly route away from adjacent tools such as soclo_newsletter_issue_create or soclo_newsletter_issue_edit.

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