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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description goes well beyond that by disclosing the shape and null semantics of each returned row (media_alt_text alignment with media_urls, created_via nullability, preview_url), which is valuable given there is no output schema. It does not mention ordering, rate limits, or auth requirements, so it falls short of a 5.

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?

Purpose is front-loaded in the first clause, which is good, but the remainder is a single dense run-on sentence with deeply nested parentheticals that is hard to scan. The field detail earns its place as an output-schema substitute, but the total lack of structural breaks hurts readability.

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?

With no output schema, the description carries the return-value burden and does so thoroughly, documenting each row field and its null conditions. It omits ordering guarantees, pagination behavior beyond the limit default, and total-count information, which keeps it short of complete.

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 both limit and status are fully documented in the schema and the baseline is 3. The description's restatement of the queue names adds marginal mapping value but no syntax or default information beyond what the schema already provides.

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 (lists) and resource (this account's posts) scoped to three named queues — drafts, scheduled, sent — which map directly to the status enum. An agent can distinguish this from list_comments or list_destinations without opening any 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?

The description names the three queues but never says when to choose this tool over alternatives such as get_post_stats or get_insights, nor does it state any prerequisite or exclusion. Usage is only implied by the status enum in the schema.

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