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 usefully discloses the payload (full text plus engagement numbers), but says nothing about behavior for a missing/invalid id or auth requirements. Adequate but with a clear gap.

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 short sentences, zero filler, with the what (fetch full text + engagement) front-loaded ahead of the when. Every clause earns its place.

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?

With no output schema, the description does the work of stating what comes back, and it does so concisely for a simple one-parameter read tool. Minor residual gaps around error/not-found behavior keep it from a 5.

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?

The single post_id parameter is 100% documented in the schema (UUID or slug), so the schema carries the burden. "by id" in the description is consistent but adds no syntax or format detail beyond it, matching the baseline for high schema coverage.

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 (Fetch), resource (post), scope (one specific post), and return content (full text + engagement numbers) identified by id. An agent can distinguish this from list_posts, search_inspiration, and get_analytics without opening any 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?

"Use when the user references a specific post and you want exact numbers" gives clear positive selection criteria — a single-post lookup rather than a list or search. It doesn't name an alternative tool or a when-not condition, but the trigger context is unambiguous.

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