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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds real context: the fetch is live rather than cached, the response includes read time and the page's own last-changed time, and long pages paginate. It stops short of saying how to detect that more content remains or any rate/error behavior.

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?

A single sentence, front-loaded with the core action and resource, that also folds in return shape and pagination without any filler. Every clause carries information.

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 no output schema, the description responsibly covers return values (Markdown content, read timestamp, last-changed timestamp) and the pagination mechanism. It is slightly incomplete on how an agent knows pagination is exhausted or what offset to resume from.

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 100%, so both path and offset are already documented in structured form, which sets the baseline at 3. The description adds only a light rationale for offset (long pages are paginated), without syntax or ordering details beyond the 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?

States a specific verb (fetch) and resource (a page from https://sitemcp.dev/), plus the output form (main content as Markdown). It implicitly separates itself from get_page_info by emphasizing content rather than metadata, but it never names or contrasts with its siblings explicitly.

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?

Usage is implied by the content-vs-info framing, and the pagination note hints at how to read long pages, but there is no explicit when-to-use guidance or named alternative (e.g., use get_page_info for metadata, search_site for discovery). Nothing is misleading, just inferred.

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