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

No annotations are provided, so the description carries the full burden. It adds valuable behavioral context about lifecycle states and visibility rules (own posts readable in any state; others only if published and visible), which is beyond schema. It does not mention permissions or errors, but the access logic is a strong disclosure.

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, front-loaded with the core action, then access rules. No filler or repetition.

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 without an output schema or annotations, the description covers purpose and access conditions adequately. It omits return format details, but with no output schema that is a minor gap; the visibility rules are the critical missing piece and are well covered.

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 the schema only defines postId as a UUID string. The description says 'by id' but adds no format details beyond what the schema provides. For a single-parameter tool with no schema descriptions, a baseline of 3 is appropriate; the description does not compensate with extra parameter meaning.

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 (Get), resource (one post's full markdown content), and key (by id). Clearly distinguishes from list_my_posts, search_posts, and get_feed, which return collections rather than a single post's content.

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 visibility and lifecycle rules effectively define when this tool will succeed versus fail, giving clear context for use. However, it does not explicitly name alternatives like search_posts or get_feed for discovery scenarios.

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