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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnly=false, and the description adds real operational context beyond them: the 10-posts/day free-plan cap, the 402 free_daily_cap reset signal, the required publish scope, and firstComment being posted the moment the post goes live. It does not explain why the action is flagged destructive (irreversibility/edits) which would complete the picture.

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 action and a lead label, then moves through prerequisites and limits without much filler. The prose is dense and slightly clipped ("at a time, in the account's next free queue slot, or now") but every clause carries information.

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 an 8-parameter mutation tool with a nested settings object and no output schema, it covers prerequisites, plan limits, scope, and media/key sourcing adequately. It omits what is returned (e.g. a post id for later posts_get/posts_approve) but nothing critical to invoking it correctly is missing.

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 baseline is 3. The description adds the queue/scheduledAt/now triad and cross-references connections_list, platforms_list and assets_upload, but largely restates what the schema already documents for each parameter.

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 up front ("PUBLISHES CONTENT: puts a post you wrote on the rail for one connected account") and clarifies scope (one account, one time, queue or now). It does not explicitly differentiate itself from the sibling posts_publish, which an agent could easily confuse with this create/publish action.

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?

Gives concrete prerequisites ("Read platforms_list first for the platform's limits and settings schema", "Needs the publish scope") and clarifies the queue vs scheduledAt vs immediate choice. It stops short of naming when to prefer a sibling like posts_publish or posts_approve instead.

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