ghost_get_newsletters

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

No annotations are present, so the description must carry the full burden. It states the tool is non-destructive ('Retrieves a list'), but lacks details about pagination behavior, rate limits, or what happens when no results are found. A read operation with minimal parameters, so a 3 is adequate.

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, concise sentence with no unnecessary words. It is front-loaded and easy to scan. Every character 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 absence of an output schema and annotations, the description should provide more context (e.g., return format, pagination details). It is sufficient for a simple list endpoint but incomplete for a fully self-contained tool definition.

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 50% (only 'filter' and 'order' have descriptions). The tool description adds no parameter information beyond what is in the schema. The 'limit' and 'page' parameters have defaults and constraints but no semantic explanation in the description, missing an opportunity to clarify pagination usage.

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 it 'Retrieves a list of newsletters from Ghost CMS with optional filtering.' However, it does not explicitly distinguish itself from the sibling tool 'ghost_get_newsletter' which retrieves a single newsletter. The name and context imply it is a list endpoint, but direct differentiation would improve clarity.

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 guidance is provided on when to use this tool versus other list or search tools (e.g., ghost_get_newsletters vs ghost_search_posts). There is no mention of pagination, limits, or appropriate filtering scenarios.

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