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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavior: a live fetch, Markdown output, source-link citation, read and last-changed timestamps, and offset pagination for long pages. It does not cover rate limits or error behavior, but it goes well beyond the annotations.

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?

The description is four compact sentences and front-loads what the tool returns. The citation instruction and pagination note are useful rather than filler. The phrase 'Returns with when it was read' is slightly awkward, which keeps it from a 5.

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 must explain the return shape, and it does: main content as Markdown, a source link, read time, last-changed time, and offset pagination. It could say more about error handling or what counts as 'main content,' but it is complete enough for correct invocation.

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 parameters are already documented in the schema. The description reiterates offset pagination for long pages but adds no syntax, format, or path-resolution detail beyond what the schema provides. Baseline 3 is appropriate when the schema handles parameter semantics.

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 and resource: 'Fetch a page ... live and return its main content as Markdown.' That is clear enough for an agent to distinguish reading page content from sibling tools like get_page_info or list_pages. It does not explicitly name a sibling for differentiation, so it falls short of a 5.

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 the tool is for reading a page's live content, but it gives no explicit when-to-use or when-not-to-use guidance relative to siblings such as get_page_info, search_site, or research_pages. It also does not explain when to paginate with offset beyond a passing mention.

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