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

Annotations already cover the safe, read-only, idempotent nature of the tool. The description adds useful behavioral context beyond annotations: the output can be Markdown or stripped text, and content is truncated at 40,000 characters. This helps the agent set expectations about size and format.

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?

One concise, information-dense sentence. The verb and resource are front-loaded, and every element—domain, format options, and character cap—contributes directly to correct invocation. No filler or redundancy.

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-only tool, the description covers the supported domain, output formats, and length limit. Annotations handle safety semantics. Minor gaps include the absence of a statement about what happens when a page exceeds the 40,000-character limit or how format is determined, but these are not critical for correct tool selection.

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%, so the description must carry the parameter's meaning. It does clarify that the url parameter refers to a specific page on the magstackonline.com domain and that output has a character limit. However, it does not explain how the output format (Markdown vs stripped text) is selected or whether the url must be a full absolute path, leaving some burden on the agent.

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 starts with a specific verb ('Read') and a precise resource ('one https://magstackonline.com page'), then adds output formats and a length limit. This clearly distinguishes it from the sibling tools search_pages and site_info without ambiguity.

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 intended use case is implied: pass a URL to fetch page content from the magstackonline.com site. However, it does not explicitly explain when to choose this tool over search_pages or site_info, or mention any exclusions such as 'use search_pages if the URL is unknown.'

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