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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds meaningful behavioral context beyond those annotations: it only reads public pages or API documentation via canonical URLs and refuses arbitrary URLs. It does not mention response format, but that is a minor gap for a read-only tool.

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?

Two sentences with no filler; the core action and source constraint are front-loaded, and the exclusion rule is placed immediately after. Every sentence 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 one-parameter read tool with strong annotations and no output schema, the description is nearly complete. The only small gaps are that resources/list is referenced without being defined or appearing in the sibling list, and return content is not described. Otherwise an agent has enough to invoke it 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 only defines url as a string with maxLength 500, and the description carries most of the semantic burden. It does so by specifying that the URL must be exact, canonical, and sourced from search_content or resources/list, and by excluding arbitrary URLs. Some further detail on what canonical means would make it completely unambiguous.

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 action ('Read'), a clear object ('full public page or API documentation'), and a precise input condition ('exact canonical URL from search_content or resources/list'). This clearly distinguishes it from siblings like search_content, which finds URLs, and read_memo/read_memory, which read stored resources.

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?

It explicitly tells the agent when to call this tool: only when an exact canonical URL has been obtained from search_content or resources/list. It also gives an explicit when-not rule with 'Never fetches arbitrary URLs', which prevents unsafe or speculative calls.

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