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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the safety profile is covered. The description adds real behavioral context beyond that: UTC instants with tenant timezone for display, ordering, rejection filtering, and what each per-item verdict (capVerdict, scheduledPublishFailedReason, waitingForTap, notices) means. It stops short of pagination, size limits, or empty-result behavior.

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?

Purpose, ordering, and exclusions are front-loaded in the first sentence, and the second sentence is devoted to return-field semantics. The trailing clause chain ('and waitingForTap ... and notices ...') is slightly run-on, but with no output schema every clause earns its place.

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 carries the return-value burden by explaining every notable field and the timezone convention. It is nearly complete for a read-only list tool; only pagination and empty-state behavior are unaddressed.

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% and the schema fully documents handle (with/without @, omit for default) and the context parameter. The description adds no parameter-level meaning, so the baseline 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?

States a specific verb and resource ('List every draft with a scheduled publish time') plus two scoping rules: soonest-first ordering and exclusion of rejected drafts. An agent can distinguish this from list_drafts or get_draft without opening any schema.

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?

The exclusion of rejected drafts and the ordering hint at when this view is appropriate, but there is no explicit when-to-use statement and no named alternative (e.g., list_drafts, edit_schedule, get_draft). Usage is implied rather than stated.

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