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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint), so the bar is lower. The description adds real value beyond them: the tool returns grounded page content, requires a public URL, and rejects competitor study-material hosts. It stops short of describing failure behavior (timeouts, paywalls, non-public URLs) or rate limits.

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?

Three tight sentences, with the core action front-loaded and the routing constraints immediately after. There is mild duplication of the sibling-routing guidance that also appears in the url parameter description, which keeps it just under a top score.

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?

An output schema exists, so return-value detail is unnecessary, and the annotations carry the read-only/open-world profile. The description covers the URL prerequisite and host restrictions; only edge-case behavior on failed or blocked reads is left unaddressed.

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% for both parameters, so the schema already documents url and the optional query extraction instruction. The description adds no syntax, format, or length guidance beyond that, making 3 the correct 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?

States a specific verb and resource ('Read a specific public URL') plus the output intent ('return grounded page content for agent evidence'), and names the siblings it is not (search-documents, search-web). An agent can distinguish it from the search tools without opening any schema.

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?

Explicit routing: use this when you already have the exact URL; use search-documents for Studocu documents; use search-web for open-web discovery. It also states an exclusion ('Competitor study-material hosts are rejected'), which is exactly the when-not guidance that prevents wasted calls.

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