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 processing and uploading but lacks details on behavioral traits like authentication requirements, rate limits, error handling, or what 'processes' entails (e.g., resizing, format conversion). This leaves significant gaps for a tool that performs multiple operations.

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 a single, efficient sentence that front-loads key actions (download, process, upload, return) without wasted words. Every part contributes to understanding the tool's workflow, making it highly concise and well-structured.

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 (multiple operations: download, process, upload) and lack of annotations or output schema, the description is insufficient. It omits critical details like input requirements (e.g., URL format), processing specifics, error conditions, and output structure, leaving the agent with incomplete guidance.

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 appropriately does not discuss parameters, earning a baseline score of 4 for not adding unnecessary information 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 tool's purpose with specific verbs ('downloads', 'processes', 'uploads', 'returns') and resources ('image from a URL', 'Ghost CMS', 'Ghost image URL and alt text'). It distinguishes from sibling tools which focus on members, newsletters, pages, posts, tags, and tiers rather than image uploads.

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 implies usage for uploading images to Ghost CMS from URLs, but provides no explicit guidance on when to use this tool versus alternatives (e.g., direct file uploads or other media handling tools). No exclusions or prerequisites are mentioned, leaving usage context somewhat vague.

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