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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description still adds real behavior beyond them: the conditional nature of the first-comment data ('while it is scheduled'), the inclusion of per-platform/account instanceLabels, and the underlying endpoint (GET /api/v2/posts/{id}). It stops short of describing behavior for missing IDs or unscheduled posts.

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?

One front-loaded sentence opening with the read-only marker and the resource, plus a compact parenthetical for the wrapped endpoint. The middle enumeration is dense but every clause maps to a distinct returned field; nothing is redundant, though the nesting of the comment clause makes it slightly hard to parse on first read.

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?

There is no output schema, so the description correctly carries the burden of enumerating what comes back and does so comprehensively, including id provenance and the conditional first-comment data. Remaining gaps are minor: no mention of error behavior for an invalid/unknown id or what a non-scheduled post yields.

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?

With a single parameter at 100% schema description coverage, the schema already fully explains `id` and its two sourcing options. The description restates the same sourcing guidance rather than adding syntax, format, or validation detail, so the baseline of 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 the resource (a post, by id) and enumerates the returned facets: status, slot, platforms, labels, per-platform instanceLabels, and first comments with editability. This is a specific verb+resource statement that separates it from get_content. It does not explicitly separate it from list_post_comments, which also deals with post comments, so it falls just 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?

It tells the agent where to get the `id` (convexPostId from publish, or posts[].id from get_content), which is useful routing information, and the phrase 'while it is scheduled' implies the tool is meaningful for scheduled posts. But there is no explicit when-to-use/when-not guidance and no named alternative for cases like inspecting all comments (list_post_comments) or the full content object (get_content).

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