read_content

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

With no annotations, the description must carry the transparency burden. It does signal a non-destructive read and specifies the resource type (HTML content), which is useful. However, it does not disclose any additional behavioral traits such as whether the full HTML document is returned, error handling, or authentication/rate-limit implications. For a simple read tool this is minimal but adequate.

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 a single sentence with no filler. The operation (read) and the resource (HTML content of a page) are front-loaded, and every word contributes to the agent's understanding.

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-required-parameter read tool with no output schema, the description is nearly complete. It communicates what the tool does and what it returns ('HTML content'), which is sufficient for an agent to invoke it correctly. The main gap is a lack of explicit response format or edge-case context, but the tool's low complexity makes this a minor omission.

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%; the pageId parameter is described as 'The ID of the page'. The tool description adds no extra meaning about the parameter beyond what the schema already states, so the baseline of 3 is appropriate.

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 'Read the HTML content of a page' uses a specific verb and resource, clearly distinguishing itself from sibling tools like list_pages (which lists pages) and create_page (which creates pages). It states exactly what operation the tool performs 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 is implied: use this tool when you need the HTML content of a specific page. However, it does not explicitly contrast it with list_pages or mention that a pageId is typically obtained from a listing operation first. No exclusions or alternative routing are provided, leaving usage to inference.

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