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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, and idempotentHint=false. The description adds genuinely useful context beyond those flags — existing receipts stay unchanged, and deduplication depends on reusing the same Idempotency-Key and settings. It does not explain the destructive scope (what a reschedule replaces or removes), which is the most important missing behavior for a destructive write.

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?

Five short sentences, front-loaded with the action, then constraints, then retry/polling advice. Dense and mostly waste-free, though the telegraphic style occasionally drops subjects and forces the reader to reconstruct the 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 five-required-parameter destructive write with no output schema and no annotations on return shape, the description covers the critical agent needs: idempotent retry, verification path via getPost/getCalendar, and non-modification of published content. Missing only the meaning of contentGroupId and any error/partial-failure behavior.

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 only 40%, so the description must carry weight. It adds meaning for postId (reuse the same ID, do not copy published content), platforms (destinations), scheduledFor (time), and Idempotency-Key (reuse after lost responses), but contentGroupId is never explained in either the schema or the description, leaving one required parameter opaque.

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 gives a specific verb and resource plus scope: scheduling an existing (possibly already-published) post to destinations it has not yet reached. It implicitly separates itself from createPost/publishPost via 'do not copy or edit published content', but never names the close siblings bulkSchedule, scheduleStory, or scheduleVideo, so an agent must still infer which scheduling tool applies.

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 gives concrete operating guidance: confirm destinations and time, reuse the same post ID, reuse the Idempotency-Key and settings after a lost response, and poll getPost/getCalendar for delivery jobs. That covers retry and verification behavior well, but there is no explicit when-not-to-use or routing to bulkSchedule for multi-post cases.

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