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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds that it returns URLs with a match score and that it is a sitemap search, giving useful behavioral context beyond the annotations. No contradiction.

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 two concise sentences with no filler. The primary purpose is front-loaded, and the second sentence adds the output format. Every word 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 simple two-parameter search tool with no output schema, the description covers the input (query) and output (URLs with match score). It does not mention pagination or result ordering, but the schema's limit and the openWorldHint annotation imply limitations. The tool is complete enough for an agent to call correctly without further clarification.

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 0%, so the description must compensate. It clarifies that 'query' refers to words in the URL path, which is helpful. However, it does not explain the 'limit' parameter or the meaning of the match score in terms of parameter usage. The query parameter's semantics are partially covered, but the limit is left to schema defaults (which are self-explanatory). Overall, partial compensation for low coverage.

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 (find pages) on a specific resource (wildorangecharters.com) using a clear method (words in URL path, sitemap search). It distinguishes from siblings: read_page likely fetches content, site_info likely provides site metadata, so search_pages is unambiguously the page-search tool.

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 the intended use case: searching for pages by URL-path keywords. It does not explicitly state exclusions or when to prefer siblings, but the distinct purposes of read_page and site_info make the choice obvious. Clear context without explicit when-not guidance earns a 4.

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