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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful constraint that only 'published' posts are readable and that the full text (not a summary) is returned, but says nothing about auth, rate limits, or behavior on a missing/unpublished post_id.

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 front-loaded sentence with no filler; the resource is named first and the parameter's provenance second.

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?

For a one-parameter read tool with no output schema, the description adequately covers what is returned and where the ID comes from, and annotations cover safety. It would be slightly better with a note on unpublished/invalid post_id behavior.

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 0% and the schema only declares post_id as a string, so the description carries the burden. It does add meaningful semantics by specifying where post_id comes from (search_posts) and that it must denote one published post, but gives no format or example.

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+resource: returns the full text of one published community post. It implicitly distinguishes from search_posts by naming it as the source of post_id, but never explicitly frames search_posts as the alternative for finding posts.

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?

'by post_id from search_posts' tells the agent this tool is invoked downstream of search_posts, giving clear usage context. It stops short of explicit when-not guidance (e.g., that it cannot retrieve drafts or multiple posts).

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