Get a page

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

No annotations provided, so description bears full burden. It discloses that the tool returns 'full HTML body', which is a key behavioral trait. However, it does not cover error cases (e.g., page not found) or permissions, but for a simple fetch, this is sufficient.

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 with no wasted words. Front-loaded: first sentence states action and result, second adds constraint. Every sentence 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 a simple fetch tool with 2 optional parameters, no output schema, and no annotations, the description covers essential aspects: what it does, how to call it (exactly one of id/slug), and what it returns (full HTML body). Completely adequate for an AI agent.

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?

Input schema has 100% description coverage (id and slug described), so baseline is 3. Description adds 'Provide exactly one of id or slug', clarifying mutual exclusivity and usage constraint, which adds value beyond 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?

Description clearly states 'Fetch a single page by id or slug, including its full HTML body.' Verb 'fetch' is specific, resource is 'page', method is by id/slug, and output includes full HTML body. Distinguishes from siblings like ghost_list_pages and ghost_get_post by specifying page vs post and single vs list.

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?

Description only gives the constraint 'Provide exactly one of id or slug.' No explicit when-to-use or when-not-to-use guidance, nor alternatives mentioned. While the constraint is useful, the agent lacks context for choosing this tool over siblings like ghost_list_pages or ghost_get_post.

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