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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe-read behavior is covered. The description adds value by disclosing the output format options (Markdown vs stripped text) and the 40,000-character cap, which are not visible in annotations. That is meaningful added context beyond the structured data.

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 compact sentence that front-loads the action ('Read one page'), includes the domain, format, and character limit. No wasted words; every element earns its place.

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 tool with one parameter and no output schema, the description covers the key facts: target domain, output format, and size limit. It doesn't explain what happens when the page exceeds 40,000 characters (truncation? error?), which is a minor gap, but overall an agent has what it needs to invoke this tool correctly.

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?

The schema has 1 parameter (url) with 0% description coverage, so the description must compensate. While the description doesn't re-explain 'url', it adds domain context ('https://continuum.blacklabelbots.com') and the character limit, which clarifies what URLs are valid and what output size to expect. With only one self-evident parameter, the description's contribution is sufficient.

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 clearly specifies the verb 'Read', the resource (one https://continuum.blacklabelbots.com page), the format (Markdown or stripped text), and the length limit (up to 40,000 characters). This distinguishes it from siblings like search_pages and site_info without needing to open those tools.

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 this tool is for retrieving a single page's content, which contrasts with search_pages (searching) and site_info (site-level info). It doesn't explicitly state when not to use it, but the domain restriction (continuum.blacklabelbots.com) and the contrast with siblings make the usage context clear.

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