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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are 'best matching' (i.e. relevance-ranked) and names the returned fields, useful context compensating for the absent output schema, but says nothing about ranking behavior, result limits interacting with the cap, or empty-result behavior.

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 front-loaded sentence that identifies the search scope, the resource type, and the return fields with zero filler. Nothing restates the name or title verbatim in a wasteful way.

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?

With no output schema, the description usefully names the returned fields (route, title, description), and the annotations carry the safety profile, so an agent has what it needs to call this correctly. Minor gaps: no mention of ranking order, limit interaction, or behavior on zero matches.

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%, with both 'query' (with an example phrase) and 'limit' (default and range) fully documented in the schema. The description adds no syntax, format, or matching-mode detail beyond what the schema already provides, so the baseline 3 applies.

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 ('Searches') and a clearly scoped resource ('the full content of this site'), then names the return shape ('route, title and description'). This naturally distinguishes it from siblings like list_pages (enumeration) and get_page_markdown (single-page fetch).

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?

Usage is implied by 'full content' search semantics, but the description never says when to reach for this instead of list_pages, get_page_markdown, or diagnose_url, and gives no exclusions or prerequisites. Adequate but leaves routing to inference.

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