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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real value beyond them by disclosing the auth requirement ("Public: no credential needed") and by signaling that the response is the complete text rather than a preview. It stops short of covering failure modes such as an unknown post_id, which keeps it at 4.

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 short clauses, zero redundancy, and the core action is front-loaded ahead of the usage condition and the auth note. Every sentence carries distinct 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?

For a single-parameter read tool with full annotation coverage, the definition supplies purpose, selection criteria, auth posture, and result granularity — enough to call it correctly. Without an output schema there is a small residual gap around what a miss (bad or unknown post_id) looks like, but nothing that would cause a mis-call.

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 100% and the property already documents the pattern and meaning of post_id, so the baseline would be 3. The description adds provenance the schema lacks — that the ID typically arrives from a message or the inbox — which tells the agent where to source the value rather than having to infer it.

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 names a specific verb and resource ("Read one offer or request in full") and scopes it to a single item via post_id, which separates it cleanly from browse_market and other list-style siblings. An agent can tell exactly 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?

It states the precise triggering condition ("when you have only a `post_id`, from a message or your inbox") and explicitly rules out the alternative case, noting that search and browse results already carry the whole text. That is a when-to-use plus a when-not-to-use in one sentence.

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