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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description's only added behavioral fact is "It will not be published," which leaves the important questions unanswered: is the draft deleted or merely flagged as rejected, can it be edited and resubmitted, and is the action reversible?

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, front-loaded sentences with no filler. Brevity is not the problem here; the sentences simply carry too little information rather than too much.

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 destructive, non-idempotent mutation with no output schema and an undocumented parameter, the description should say what state the article ends in and what the agent gets back. It supplies only a one-line outcome hint, leaving the agent to guess the post-call state.

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?

The single required parameter articleId has 0% schema description coverage, so the description is the only place to clarify it — yet it never mentions the parameter or what it identifies (article vs. draft vs. run ID). The format/pattern in the schema helps validate the value but not its meaning.

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 pairs the verb "reject" with the object "a draft" and adds the outcome "will not be published," so the basic action is legible. However, "draft" is ambiguous in this catalog: siblings include soclo_autopilot_reject_draft, soclo_newsletter_issue_reject, soclo_creators_pitch_reject, and soclo_leads_reject, and the description never says which kind of draft (the article, per the title) this targets.

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?

There is no when-to-use guidance and no mention of the obvious alternative, soclo_articles_approve, or of prerequisites such as the article needing to be in a reviewable state. The agent must infer the decision context entirely from the name and title.

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