List posts

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

No annotations provided, so description carries the burden. Mentions return of 'slimmed metadata (no full body)', which is useful behavioral info. However, lacks details on authentication, rate limits, or side effects beyond the read operation.

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 that front-load the core purpose. Every sentence adds value without unnecessary detail.

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?

Covers optional filtering, pagination, and slimmed output. Lacks details like default sorting, return structure, or behavior when no results. Adequate but not fully comprehensive for a listing tool with no output schema.

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 tag and status have descriptions). Description adds no extra meaning for parameters beyond what schema provides. Baseline of 3 is appropriate given moderate coverage and no additional semantic enrichment.

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?

Describes listing posts with optional status/tag filtering and pagination. Clearly distinguishes from sibling tools like 'ghost_get_post' (single post) and 'ghost_list_pages' (different resource).

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?

Implies usage via filtering and pagination options, but does not explicitly state when to use this tool versus alternatives (e.g., 'ghost_get_post' for a single post). No when-not or alternative recommendations.

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