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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description's job is to add consequence detail — and it does: 'Goes live on the real platform' and the tg caveat 'into every target chat, one after another,' which signals sequential multi-target dispatch and partial-failure risk. It still doesn't say whether a partial tg failure is rolled back or what the caller gets back on error.

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?

Front-loaded with the bracketed verb tag and the core action, then parameter conventions, then the side-effect note. Every clause carries information an agent needs; nothing is padding.

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 destructive, open-world tool with no output schema and no schema descriptions, the definition covers action scope, parameter formats, and live-side-effect behavior. It is missing only the post-call picture: failure/partial-success semantics and what is returned after publishing.

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 0% and the schema carries no enum, so the description does real work: it enumerates the platform codes (ig|fb|tw|tt|yt|li|th|tg) and explains that post_id is a platform-scoped id or that post_uuid may be passed instead. It leaves open whether post_id and post_uuid are mutually exclusive or which takes precedence when both are supplied.

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 a specific verb+resource (publish_social_post) and pins down the exact scope: a draft/scheduled post published immediately, or a FAILED post retried. That scope implicitly separates it from create_social_post and schedule_social_post, though neither sibling is named explicitly, which keeps it just short of a 5.

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 parenthetical '(or retry a FAILED one)' and 'publish ... right now' give a clear condition for selecting this tool over scheduling or creating. It stops short of explicit when-not-to-use guidance or calling out the sibling tools by name.

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