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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable details: returns plain text (HTML stripped, truncated) and emails, treats content as untrusted data (security warning), rate-limited to weekly quota, and refuses private URLs. No contradictions with 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 concise (3 sentences) and front-loaded with purpose. Every sentence adds distinct value: purpose, return format & security note, and constraints (rate limit, private refusal). No redundant or vague language.

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?

Given the tool's simplicity and strong annotations, the description covers purpose, usage, return values, security, and constraints. It lacks only an explicit output schema reference, but the description adequately describes what is returned. For a straightforward fetch tool, this is sufficient.

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 100%, so the schema already documents both parameters. The description reinforces the 'public http(s)' nature of the URL and mentions default/max for max_chars implicitly via schema. It does not add new parameter details beyond what the schema provides, meeting the baseline.

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 states the verb 'Fetch', the resource 'PUBLIC web page', and the use case 'context when writing/editing messages'. It provides concrete examples (prospect's website, article) and distinguishes from internal pages by emphasizing 'PUBLIC' and noting private addresses are refused.

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 gives clear when-to-use guidance ('when writing/editing messages', 'read a prospect's website or an article') and an explicit exclusion ('private/internal addresses are refused'). It does not directly mention sibling tools as alternatives, but the context is clear enough for an agent to decide.

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