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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered; the description's 'Read-only' line is largely redundant. It does add genuine behavioral context by describing the returned content and the edge case where a post has no workflow and returns status `none`.

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?

Front-loaded with the payload description, then the usage trigger, then edge cases; each sentence earns its place. The standalone 'Read-only.' fragment restates the readOnlyHint annotation and is the one piece of low-value content.

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?

There is no output schema, so the description carries the return-value burden, and it does so by enumerating what the approval review contains plus the `none` status for posts without a workflow. Combined with annotation-covered safety, an agent has everything needed to call and interpret it.

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 100% and there is a single required `id` parameter already documented in the schema, so per calibration the baseline is 3. The description adds no syntax or format detail about the post ID beyond what the schema provides.

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 (read) and resource (the approval review of a post) and enumerates the exact payload: workflow steps, approvers, decisions, rejection reason, and comment thread. This clearly distinguishes it from approve_post, reject_post, and get_post, which an agent can tell apart 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?

Gives explicit trigger conditions keyed to a sibling's output: use it when get_post shows status `rejected` or `in_approval`, with the purpose spelled out for each case. It also names the fallback behavior (a post without an approval workflow returns `none`), leaving nothing to inference.

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