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

With no annotations, the description carries the full burden. It usefully discloses the search scope (URL path only, not page content) and the return shape ('URLs with a match score'), which is valuable given there is no output schema. It says nothing about read-only status, result limits, pagination, 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?

Two short sentences with zero filler; the purpose and scope are front-loaded and the return shape follows immediately. Nothing is wasted.

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 with no output schema and no annotations, the description covers what it searches and what it returns. It still leaves query syntax (single vs. multiple terms, matching rules) and result-count behavior unaddressed, which an agent would need to guess at.

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 0%, so the description must compensate. It adds real meaning for 'query' by stating the terms are matched against URL path words (implying free-text token matching against paths, not page bodies), but it says nothing about multi-word/AND-OR behavior. The 'limit' parameter is at least self-documenting in the schema via default and min/max.

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 gives a specific verb ('Find'), a scoped resource ('pages on blbestate.com'), and the matching mechanism ('words in their URL path (sitemap search)'). This clearly separates it from content-oriented siblings like read_page, though it never names an alternative explicitly.

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 parenthetical '(sitemap search)' and the URL-path scoping imply this is a URL/title lookup rather than a full-text content search, which hints at when to prefer it over read_page. However, no explicit when-to-use, when-not-to-use, or named alternative is given.

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