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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, non-open-world), yet the description adds substantial behavior beyond them: the meaning of error_message and retry_count on failed posts, the enumerated cancel reasons on deleted posts (account_disconnected, account_deactivated, connection_lost), and the retention rule that Chirpie never removes post history. That is real disclosure an agent could not get from the structured fields.

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 purpose and filters are front-loaded in the first sentence, and the return-field detail follows. The middle sentences on error_message/retry_count are dense but relevant for a tool with no output schema; a tighter edit could trim redundancy around the hidden/deleted cases.

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 usefully explains the returned fields (platform_post_url, hidden, error_message, retry_count) and the delete/hide behaviors. Gaps remain around pagination/limit behavior and the group_id fan-out semantics, which are only covered parenthetically in the schema.

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 schema already documents limit, status, group_id, account_id and include_hidden, making 3 the baseline. The description reinforces the include_hidden/hidden relationship but says nothing about limit, group_id, or account_id beyond what the schema provides, so it adds no meaningful parameter semantics.

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 opening two sentences state a specific verb and resource (list recent posts) plus the supported filters (status, account). It clearly differs from non-list siblings like chirpie_get_post or chirpie_post, but it never names a sibling or explicitly contrasts with get_post, so it stops short of a 5.

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 rather than stated: the reader learns that hidden posts are excluded unless include_hidden is true and that drafts are only returned with an explicit status filter (the latter lives in the schema, not the description). There is no explicit when-to-use-this-vs-alternative guidance, such as chirpie_get_post for a single post or chirpie_list_comments for comments.

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