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

With annotations only flagging this as destructive/non-idempotent/open-world, the description supplies the missing operational truth: it publishes only to unreached destinations, keeps already-published content unchanged, returns acceptance rather than delivery confirmation, and forbids new keys on uncertain retries. That is exactly the context the hints cannot convey.

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?

The approval precondition and publishing scope are front-loaded, and each following sentence adds a distinct, actionable fact (idempotency, response semantics, polling, retry rule) with no filler.

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?

There is no output schema, and the description compensates by defining the return as acceptance only and routing the agent to getPost for real results. Combined with partial-publish and idempotency semantics, an agent has everything needed to call and interpret this correctly.

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 already 80%, so the bar is met by the schema alone, but the description adds real meaning: the platforms list is effectively filtered to destinations not yet reached, and the Idempotency-Key must be one per approved request and reused with identical settings. It still does not explain facebookTarget/linkedinTarget selection, which is left entirely to the schema.

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 ('publish now' a content group's drafts to specified social destinations) and scopes it to destinations the content has not already reached. It implicitly separates itself from scheduling siblings via 'publish now' and from read paths by pointing at getPost, but never names schedulePost or publishStory/publishVideo explicitly.

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 states a clear precondition ('after the user approves the content group, draft and exact social destinations') and a clear follow-up path ('poll getPost for platform IDs and results'), plus a hard retry rule. It stops short of explicit when-not-to-use guidance, e.g. that this is not the tool for scheduling or for stories/video.

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