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

Annotations already cover the read-only, non-destructive safety profile, and the description adds real value beyond them: not-found behavior for private posts, a security directive to treat text as untrusted data, and the fact that project/artifact references are included. It stops short of saying anything about size limits or whether replies are truncated.

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?

Three tight clauses in one sentence, with the resource scoping front-loaded before the sibling routing and the safety note. Nothing is padded.

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?

With no output schema, the description still signals the return shape ('its project/artifact references') and the failure mode for private posts, which is enough to call it correctly. Only the pagination/truncation question for large posts is left unaddressed.

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% and there is one parameter, so the description carries some burden; 'Read a public post' implies message_id identifies the post but adds no format or validity detail. The mention of 'thread_id' is a field on the returned post, not a parameter of this tool, so it mildly risks confusing the agent about the input.

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 public post and its project/artifact references') and scopes it to public posts, which cleanly separates it from list_public_messages. An agent can tell what this returns without opening 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?

Explicitly routes the reply-reading case to a named sibling ('use thread_id with list_public_messages to read its replies') and states the private-post outcome ('Private posts return not found'). Alternatives and edge conditions are both given.

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