Get a Ghost post

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds that the payload includes HTML, Lexical content, and full SEO/social metadata, which is genuine behavioral context, though this partly duplicates the output schema.

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 naming the action, lookup key, and payload scope with zero filler. 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?

For a read-only single-parameter tool with an output schema and full annotation coverage, this is nearly complete. It omits edge-case behavior such as what happens when the ID/slug doesn't match any post, which would help the agent handle failures.

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 0% schema description coverage on the single parameter, the description must carry the load, and it does: it clarifies that id_or_slug accepts either a Ghost ID or a slug and that the value must be exact (no fuzzy matching). That adds real meaning beyond the bare 'string, minLength 1' 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?

States a specific verb (Get) and resource (one post) with a clear scope of 'one' that separates it from list_posts, and names the lookup keys (Ghost ID or slug). It doesn't explicitly differentiate itself from the near-sibling get_page, but the resource noun does the work.

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: the word 'exact' signals that a precise identifier is required rather than a search, which is useful. However, no when-to-use vs when-not guidance or alternatives (e.g., list_posts, get_page) are named.

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