Get a post

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

With no annotations provided, the description carries full burden. It discloses the primary behavior (fetching a single post with HTML body) but does not mention read-only nature, auth requirements, or side effects. For a simple read operation, this is minimally adequate but could be more explicit.

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?

The description consists of two concise sentences with no wasted words. It front-loads the core purpose and follows with a critical usage constraint. Every sentence 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?

Given the tool's simplicity (two parameters, no nested objects, no output schema), the description is largely sufficient. It covers the action, identifier options, and return detail (HTML body). A minor addition about the return structure could improve completeness, but current info is adequate.

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 100% with both id and slug described as 'post id.' and 'post slug.' respectively. The description adds the important constraint 'Provide exactly one of id or slug', which is not enforced by the schema (both are optional). This adds meaningful usage guidance beyond the schema.

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 clearly states the verb 'Fetch' and the resource 'a single post', specifying the retrieval method 'by id or slug' and the additional detail 'including its full HTML body'. It effectively distinguishes from sibling tools like ghost_list_posts (list multiple posts) and ghost_get_page (different resource).

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 explicitly states 'Provide exactly one of id or slug', giving a clear constraint on parameter usage. It does not, however, explicitly compare to sibling tools or provide when-to-use vs. when-not-to-use guidance, though the sibling names imply differentiation.

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