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

Annotations already declare readOnlyHint and openWorldHint, covering the read-only nature. The description adds behavioral context by specifying that it returns 'main content as Markdown' (implying filtering of navigation elements) and mentions pagination with offset for long pages, which goes beyond the annotation coverage.

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 sentences, front-loaded with the main action, no wasted words. It efficiently communicates the purpose and the key pagination 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?

For a simple read-only tool with two parameters and no output schema, the description is adequate. It specifies the return format (Markdown), the pagination mechanism, and the base URL. It does not explain error handling or what happens for missing pages, but those are not critical for a read operation with read-only annotation.

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 parameters are already documented. The description adds a small clarification that offset is used for pagination of long pages, reinforcing the schema's 'Character offset for long pages'. This adds marginal value 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?

The description states a specific verb 'Fetch' and a specific resource 'a page from https://sitemcp.dev/' and specifies the output as 'main content as Markdown'. It clearly differentiates from sibling tools like get_page_info (likely metadata) and list_pages (listing) by focusing on content retrieval.

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?

The description implies its usage: to fetch page content, but it does not explicitly mention when to use this tool over alternatives such as get_page_info or list_links. No exclusions or conditions are provided, leaving the agent to infer from the description alone.

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