Get post

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety and external-dependency behavior is covered. The description adds value by disclosing the shape of the result (nested accounts with permalinks and overrides, plus media), but says nothing about behavior on a missing or inaccessible postId, nor about pagination or size.

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?

A single front-loaded sentence that names the resource and the returned components with zero filler. Every clause ('accounts (permalinks, overrides)', 'media') conveys actual 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?

With no output schema, the description does a fair job sketching return contents, and annotations cover the read-only profile. However, for a getter the agent still lacks guidance on identifier semantics and failure modes, which are the two things that actually affect a correct call.

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 coverage is 0%, so the description must carry the burden for postId, and it does not. It never says whether postId is the internal post identifier versus an external/platform post ID, nor what format is expected. This is a real ambiguity for the single required parameter.

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 verb and resource are explicit ('Fetch one post') and the singular 'one' implicitly distinguishes it from list_posts. It also names what is returned (accounts, permalinks, overrides, media), giving a concrete picture of the payload. It stops short of naming the sibling explicitly, which keeps it out of 5 territory.

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?

Usage is only implied: fetching by a single postId suggests retrieving a known post rather than browsing, which contrasts with list_posts. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as list_posts or get_post_analytics.

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