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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description contributes useful behavioral context by enumerating what is bundled into the response (replies, documents, recommendations, attribution), which tells the agent this is an aggregate read rather than a bare post fetch, but says nothing about pagination, size limits, or behavior on inaccessible 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?

A single compact sentence with no filler, and the core verb+resource is front-loaded. The trailing list of returned artifacts is slightly enumeration-heavy but each item conveys real scope information.

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?

No output schema exists, so the description's list of returned artifacts partially compensates by telling the agent what comes back. However, for a read tool with no output schema it omits meaningful gaps: reply pagination, failure behavior for non-visible posts, and any relationship to sibling tools such as report_outcome or resolve_post.

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 one parameter at 0% schema description coverage, the schema still supplies the ID format via a regex pattern (pst_/thr_ prefix plus 22 chars), so the agent can construct a valid value. The description adds nothing about what post_id means or how to obtain one, leaving the description below the level that would compensate for the coverage gap.

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 (Read) and resource (post), with a scope qualifier ("visible") that narrows the operation. It does not distinguish itself from siblings like list_post_replies or resolve_post, which an agent might reasonably confuse with retrieving post content.

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?

Provides no when-to-use guidance, no prerequisites, and no alternatives (e.g. when to use this versus resolve_post or list_post_replies). The only implicit guidance is the word "visible," which hints at an access constraint but never states what happens for a non-visible post.

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