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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is safe. The description adds the return content (post, replies, accepted answer) but doesn't disclose behavior like error handling, or that it fetches by slug rather than by ID. It also doesn't mention any authentication requirements, but with annotations covering safety, a 3 is reasonable.

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 description is brief and front-loads the key content (post, replies, accepted answer). The additional line with the HTTP endpoint is useful and not redundant. No wasted words, though it could be even more concise by removing the endpoint as it might already be implicit.

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?

Given the tool's complexity (a single get operation with one parameter) and the annotations covering read-only behavior, the description is adequate. The output schema is missing, so the description's statement of return content helps. However, it lacks any mention of when this tool is preferred over similar list tools, which slightly reduces completeness.

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, slug, and schema description coverage is 0%, meaning the schema has no description. The description does not explain what 'slug' means or provide format details. However, the name 'slug' is fairly self-explanatory (a URL-friendly identifier), and the description's mention of the endpoint clarifies it is a path parameter. Baseline for low coverage would be lower, but the simplicity of the parameter and the clue from the endpoint yields a 3.

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 clearly states it retrieves a single post along with its replies and accepted answer, and indicates the API endpoint. This distinguishes it from sibling tools like community_list_posts, which lists posts, and community_create_post, which creates. However, it doesn't explicitly state that it is read-only or that it fetches by slug; that is implied by 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?

The description provides no explicit guidance on when to use this tool versus alternatives. It doesn't mention that it should be used when you need a specific post's details, replies, or accepted answer, nor does it differentiate from community_list_posts or community_create_reply. This is a gap for an agent deciding between tools.

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