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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds what the returned document contains (choice lists sourced from the network, not_available reasons, per-format media rules) but does not disclose cost, latency, or freshness of the network reads, which matters for a tool whose output changes as boards/pages/playlists change.

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?

A single run-on sentence packing a dozen concepts and nested parentheticals, followed by terse fragments ("lists.<name>.field says where each choice goes"). The most actionable instruction – read options_schema before setting per-platform options – is buried at the very end rather than front-loaded.

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 must describe the return shape, and it does enumerate the top-level keys (lists, not_available, options_schema). However the enumeration is impressionistic rather than structural, leaving the agent to infer the overall document layout for a fairly complex payload.

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 100%, so the baseline applies. The description does add real meaning beyond the schema by explaining that supplying `subreddit` yields that subreddit's flairs and its flair rule, and that `account_id` scopes the returned schema to options.targets[<this account id>]. That is useful, but it is folded into a dense clause rather than stated plainly.

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 clearly identifies the resource: the per-account posting rules and option choices (text limits, formats, required fields, choice lists, not_available, options_schema). It omits an explicit verb ("Returns" / "Get") and reads as a payload enumeration rather than a crisp verb+resource statement, but the substance is unambiguous and is clearly distinct from the analytics/listing siblings.

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?

Closes with explicit usage direction: "Read it before you set per-platform options" for create_post's options.targets[<account id>], which tells the agent exactly when this tool is the prerequisite. It does not name an alternative or exclusion, but the sibling set (analytics, listings, scheduling) has no real overlap, so the guidance is sufficient in context.

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