List pages

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

No annotations exist, so the description carries the full burden. It discloses that results are slimmed (no full body) and that pagination and filtering are supported, which is useful. However, it does not mention error behavior, default filtering behavior (e.g., default status is 'all'), or authentication requirements.

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?

Two concise sentences, front-loaded with the action and key features (filtering, pagination, slimmed metadata). Every sentence adds value with no redundancy.

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?

With 4 parameters and no output schema, the description is somewhat incomplete. It mentions slimmed metadata but does not specify which fields are returned, how pagination works in practice, or whether filters are combinable. Adequate but leaves gaps for a tool of moderate complexity.

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 50% (tag and status have descriptions; page and limit do not). The description mentions tagging, status, and pagination at a high level, adding context beyond the schema's individual descriptions. But it does not elaborate on each parameter's format or constraints, leaving the schema to do more work.

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 lists pages, with optional filtering by status and tag, and pagination. It distinguishes itself from siblings like ghost_list_posts by specifying 'pages' and notes it returns slimmed metadata, differentiating from ghost_get_page which would return full content.

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 listing pages with filters, but does not explicitly guide when to use alternatives like ghost_get_page or ghost_list_posts. No exclusions or when-not-to-use advice is given.

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