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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the return is the full markdown body and it yields null when the page is not visible to the caller, which flags permission/visibility scoping rather than a hard error.

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 compact sentences, front-loaded with the verb and resource, with zero filler. Each clause adds a distinct fact: scope of payload, read-only nature, and null-return behavior.

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?

There is no output schema, so the description carries the return-value burden and does so: full markdown body plus null on missing/invisible pages. Combined with annotations covering safety and a single required param, nothing essential for correct invocation is missing.

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 0% and the single page_id property carries no description, so the description's phrase "by id" is the only clarification offered. It does not say whether the id is numeric or a slug/key despite the schema allowing integer or string, leaving the agent to guess the accepted identifier form.

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 and resource ("Read a single personal wiki page by id") and immediately scopes the payload ("the full markdown body, not just list metadata"), which separates it from list_wiki_pages without naming it. An agent can distinguish this from the other wiki siblings at a glance.

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 the selection rule clearly: use this when you need the page body rather than list metadata. It does not explicitly name list_wiki_pages or state when-not to use it (e.g., for bulk retrieval), so it stops short of full routing guidance.

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