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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds real behavioral context beyond that — that own posts surface moderation status values (queued, review, published, rejected, deleted) and a rejection reason — which is genuinely useful. It still omits what a non-owner/published fetch returns and any auth requirement.

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?

It is short and contains no filler, but it is an awkward sentence fragment with no leading verb, so the key action is not front-loaded. Brevity here comes at the cost of grammatical clarity rather than from disciplined editing.

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 must carry the return-value burden; it covers the moderation-status case reasonably well but says nothing about what a published story response contains or how errors/not-found are handled. For a single-param read tool this is adequate but leaves clear gaps.

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?

With one parameter at 100% schema description coverage, the baseline is 3. The description adds nothing about the id beyond what the schema's 'The post id' already says, such as whether it accepts slugs or only opaque ids.

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 is a noun phrase describing the return payload rather than stating a verb+resource action; the verb is only inferable from the name/title. It does convey a meaningful distinction (published story vs. your own post's moderation status), but it never differentiates from the sibling check_story, which sounds like it does something very similar.

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 guidance on when to call this versus browse_posts, search_posts, or especially check_story. The only implied usage cue is the 'for your own' clause, which hints at an ownership condition but states no prerequisite or exclusion.

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