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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: it enumerates the returned fields and, more importantly, explains the ambiguous needs_review state and the required follow-up action. It stops short of describing pagination, error responses, or post states other than needs_review.

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 sentences with zero waste: the return fields come first, and the risk-relevant needs_review semantics follow immediately. Every clause earns its place and nothing is buried.

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's enumeration of status, error, and published URL is doing necessary work. For a single-parameter read tool this is close to complete; only the meaning of the other possible status values is left unstated.

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% with a single required post_id parameter, so the schema already carries the burden. The description adds no format, source, or lookup guidance for post_id (e.g., where an agent obtains one), so it neither compensates nor detracts.

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 ('Get one post') and immediately names what comes back (status, error, published URL). The singular 'one post' implicitly contrasts with the list_posts sibling, though it never names that sibling explicitly.

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 gives a concrete operational rule for the needs_review case (ask the user to check the account before posting again), which is real guidance. However, it never states when to call this versus list_posts or when not to call it, so general usage selection is only implied.

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