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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description goes further: it reveals side effects (world-readable immediately), quota consumption, and a warning mechanism in the response ('response warns when the allowance is nearly spent'). Loses one point for not explicitly stating retry or rate-limit behavior, which would have made it a 5, but this is strong, non-annotation-redundant context.

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 tight paragraphs: what it does, what to watch out for (non-idempotency), and operational specifics (quota, return values). Every sentence carries signal; no filler. Bolded 'PUBLISHES' effectively signals emphasis. Appropriate length for a high-stakes, non-idempotent, resource-consuming operation.

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 6-param tool with no output schema and no nested objects, the description covers the critical behaviors: immediate visibility, scheduling semantics, non-idempotency, quota, and return value fields (public url, editor_url). Slight deduction for not stating whether the quota applies per-request or per-publish (edge case) and not mentioning rate limits, but the description exceeds what a typical tool description offers at this complexity level.

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 100% with detailed per-parameter descriptions already. Description adds meaningful behavioral meaning beyond the schema: context for what 'published' means for schedule_at, the fact that omitting schedule_at publishes immediately, and that a past timestamp publishes immediately. This helps the agent reason about edge cases without re-stating what the schema already documents.

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?

Uses a specific verb+object construction ('Create a new article and make it live immediately, or schedule it') immediately followed by the operational implications. Clearly distinguishes from create_draft (the sibling) by stating what publishing means. The all-caps PUBLISHES reinforces the permanence and visibility semantics without redundancy.

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?

Explicitly provides when-to-use and when-not-to: 'If the piece is not ready, use create_draft instead and publish later.' Names the alternative tool, explains the consequence of misuse (double publish), and points to update_article for modifications. Also warns about non-idempotency, which is a usage red-flag with decision-relevant consequences.

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