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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds meaningful context beyond that: it discloses the key return field (`_id`) needed to chain into other tools and clarifies the 'not yet posted' boundary. It stops short of describing ordering, limits, or whether failed/paused items are included, so it is not fully transparent.

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-loads the resource and scope in the first sentence, then moves to actionable routing instructions. Every sentence carries operational value; there is no restatement of the name or title.

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 one-optional-parameter read tool with no output schema, the description supplies enough: what is returned in principle and the identifying field needed for follow-up calls. Minor gaps remain around result ordering and volume, but nothing blocks correct invocation.

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% and the single optional `social_set` parameter is documented in-schema as accepting a name, id, or handle, with omission meaning every set. The description adds nothing about this parameter, which is acceptable but earns only the baseline.

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 ('Get a list of the user's scheduled posts (tweets) or scheduled retweets') and narrows the scope to those 'that have not yet been posted,' which separates it from draft- or history-oriented siblings. An agent can identify the resource and its state filter without opening the schema.

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 explicit follow-on routing: cancel/unschedule/remove -> unschedule_post with the `_id`, cross-posting to other networks -> cross_post with the `_id`, and one call per `_id` for bulk cancellation. It even pre-empts a wrong alternative ('Do not tell them to use the Calendar unless the tool fails'), which is exactly the when-not guidance most definitions lack.

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