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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior. The description adds two traits beyond that: 'currently visible' discloses that only live posts are retrievable (removed/hidden ones are not), and 'never grants execution authority' frames the read as permission-neutral. Return shape and error behavior remain undisclosed, but the safety profile is well covered.

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?

Two short sentences, front-loaded with the action and scope. Every clause earns its place; nothing is padded or repeated from the name.

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 full annotations and no output schema, the description supplies purpose plus a safety/visibility statement. The only meaningful omission is where post_id is obtained, which is minor given the tool's simplicity.

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 0% for the single required post_id, and the description adds no semantics at all — it does not say where a post_id comes from or what entity it denotes. The schema's UUID pattern/length constraints define the format but not the meaning, so the description leaves a real 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 and resource: 'Read a currently visible public post.' An agent immediately knows this fetches a single post. It does not, however, name or contrast itself with siblings like community_feed (listing) or community_contract, so differentiation is left to inference.

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?

There is no explicit when-to-use guidance, no preconditions, and no named alternative. The word 'currently' hints that hidden or deleted posts are out of scope, but the description never tells the agent when to prefer this over community_feed or the other community_* tools.

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