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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read only' is redundant but consistent. The genuinely additive detail is the 20-item cap; the run-down of returned fields is largely duplicated by the output schema. No contradiction, but the description stops short of discussing pagination or ordering beyond 'latest'.

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?

The core fact (latest 20 posts on a channel you run) is front-loaded in the first clause, and the trailing field enumeration is dense but follows naturally. Slightly long and list-heavy, and the field roster partly duplicates the output schema, but there is no filler or repetition.

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 an output schema present, the description needn't explain return values, and it still names the fields that matter for downstream calls. Combined with a fully described single optional parameter and read-only annotations, an agent has everything needed to call it correctly; only ordering/pagination behaviour is left unstated.

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?

There is one parameter and the schema documents it at 100% coverage, including the 'key from list_identities or its name' form and the 'may be left out when only one fits' fallback. The description only gestures at it as 'a channel the person runs' and adds no syntax or edge-case detail beyond the schema, so the baseline 3 applies.

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 names a precise verb and resource ('The latest posts ... on a channel the person runs or writes news for') and adds a hard cap (up to 20), which immediately separates it from create_post, schedule_post, delete_post and edit_post in the sibling list. An agent can tell what it retrieves and from where 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?

Usage is implied by the parenthetical '(for edit_post, delete_post, read_comments)', which signals that this is an entry point for post-management workflows, and by the constraint that the channel must be one the person runs. However, it never states when to prefer this over neighbouring reads like list_my_channels or read_comments, nor any exclusion. Adequate but not explicit.

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