Ghost MCP Server

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

No annotations are provided, so the description carries full burden. It mentions that pages don't typically use tags, adding some behavioral context, but fails to disclose critical traits like required permissions, whether creation is idempotent, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is inadequate.

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 is two sentences with zero waste: the first states the core purpose, and the second adds crucial differentiation. It's appropriately sized and front-loaded, with every sentence earning 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 complexity (a mutation with no annotations or output schema) and the description's brevity, it's partially complete. It covers purpose and a key distinction from posts, but lacks details on behavior, permissions, or outcomes, leaving gaps for an AI agent to invoke it correctly.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description adds value by clarifying that pages don't typically use tags, which is semantic context beyond the empty schema, though not directly about parameters.

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 action ('Creates') and resource ('new page in Ghost CMS'), making the purpose evident. It distinguishes from sibling tools like 'ghost_create_post' by noting pages don't typically use tags, but doesn't fully differentiate from other create operations (e.g., 'ghost_create_member').

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 provides clear context by specifying when NOT to use tags (unlike posts), which helps differentiate from 'ghost_create_post'. However, it lacks explicit guidance on when to use this tool versus other create tools (e.g., 'ghost_create_member') or prerequisites for page creation.

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