ghost_get_posts

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

No annotations are provided, so the description carries full burden. It states 'retrieves' indicating a read operation, but does not disclose authentication needs, rate limits, side effects (none expected), or pagination details beyond schema. Minimal behavioral context.

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?

Single sentence that is front-loaded with the core action. Every word contributes meaning; no redundancy or fluff.

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?

Despite many parameters and no output schema, the description does not explain return structure (e.g., array of posts with pagination meta) or how to interpret results. Basic completeness is lacking for complex usage.

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 description coverage is 75% (6 of 8 parameters have descriptions). The tool description adds no extra meaning beyond the structured schema. The baseline 3 is appropriate given high schema coverage, but the description does not compensate for the undocumented limit and page 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 states 'Retrieves a list of posts from Ghost CMS with pagination, filtering, and sorting options.' This clearly identifies the verb (retrieves), resource (posts from Ghost CMS), and key capabilities (pagination, filtering, sorting). It distinguishes from siblings like ghost_get_post (single) and ghost_search_posts (search).

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?

No explicit when-to-use or alternatives are mentioned. The description implies usage for listing posts with options, but does not differentiate from ghost_get_post or ghost_search_posts. Given the large sibling list, better guidance would improve score.

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