Get one of my dochost pages

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

Annotations already mark read-only/non-destructive; the description adds the crucial privacy behavior that body and password are never returned, and enumerates exactly which fields the caller can expect. This goes well beyond the structured annotation data.

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 short sentences: the first delivers the resource and returned fields, and the second adds a critical exclusion. No filler or unnecessary repetition.

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?

For a one-parameter read with an output schema and annotations, the description is nearly complete: it identifies the selector, enumerates returned fields, and flags excluded data. The only notable gap is not pointing to list_my_pages for discovering slugs or enumerating pages.

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?

The description confirms slug is the page identifier, but the schema already names the parameter. With 0% schema description coverage, it only partially compensates by clarifying the slug selects one of 'your' pages; no format, origin, or example is given.

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?

States a specific verb ('Get'), a precise resource (one page by slug), and the exact metadata fields returned. 'One of your pages by slug' distinguishes it from list_my_pages (plural enumeration) without needing the sibling 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?

Clear context: use when you need a single page's metadata and have its slug. It does not explicitly name alternatives or say when not to use it, so no exclusion guidance is provided.

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