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

Annotations already declare non-read-only, idempotent, open-world, non-destructive behavior, so the bar is lower. The description usefully adds the return shape (ScheduledPost records with per-platform delivery status and timestamps) and that retry re-dispatches failed deliveries, but says nothing about whether delete is permanent, whether updates affect already-published posts, or what retry_failed does on success. Note: destructiveHint=false sits uneasily with the advertised delete action, though that is an annotation-to-capability tension rather than a description contradiction.

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 tight sentences: capabilities and target store first, use cases second, return shape last. No filler, nothing buried.

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 six-parameter, action-dispatched tool with no output schema, the description covers what the tool reaches, when to use each action, and what comes back. It stops short of per-action preconditions (e.g., retry_failed only meaningful when deliveries failed, delete irreversibility), which is the main remaining gap.

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 the schema already explains action, postId, content, profileId, scheduledFor, and statusFilter with per-action conditions. The description adds no syntax, defaults, or edge-case detail beyond that, so 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?

Names specific verbs (list, inspect, update, delete, retry) against a concrete resource (scheduled/queued/published social posts in Nuntior Cloud). Scope is unambiguous, though it never explicitly contrasts with the sibling posts_publish, which an agent could confuse for the update/publish boundary.

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?

Enumerates concrete use cases mapped to actions: auditing the content calendar, editing copy or timestamps before publication, removing cancelled posts, retrying failed deliveries. Clear context for when to reach for it, but no explicit exclusions or named alternatives.

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