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

Annotations already declare non-read-only, non-idempotent, non-destructive, open-world. Beyond that, the description contributes two real facts: the call is free (no credits) and the created issue lands in a draft state gated on owner approval — neither of which the annotations convey. It does not say what is returned or whether re-calling duplicates the draft (relevant given idempotentHint=false).

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?

Two short sentences, zero filler, with the key behavioral fact (draft/approval) placed immediately after the action. Slightly under-specified rather than padded, so it is efficient but not maximally informative per sentence.

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 3-parameter mutation with no output schema, the description covers the lifecycle stage but omits what the call returns (issue identifier for later approve/edit), whether duplicate calls create duplicates, and how this differs from the sibling edit/issue tools. Adequate but with clear gaps an agent would hit on first use.

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?

At 67% schema coverage the schema documents body formatting and preheader meaning, but 'subject' carries no description. The tool description adds nothing about any parameter, so it neither compensates for the undocumented subject nor adds formatting guidance beyond the schema. Baseline 3 fits.

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+resource ('Save an issue') and adds the qualifier 'the owner wrote', which separates it from AI-generated drafts (soclo_newsletter_draft). It does not explicitly distinguish itself from soclo_newsletter_issue_edit or soclo_newsletter_issue, so sibling differentiation is partial.

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 starts as a draft that the owner must approve' implies the workflow position (create now, approve later) but never names soclo_newsletter_issue_approve, soclo_newsletter_issue_edit, or soclo_newsletter_send as the next/alternative steps. Usage is inferable rather than stated.

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