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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely useful context—sitemap-based search and that results carry a match score—but does not go deeper into edge cases, score semantics, or result-set behavior. No contradiction with annotations.

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 tight, front-loaded sentences with zero waste. The purpose, domain, search method, and return promise are each conveyed in a single efficient statement.

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 read-only, idempotent search with 2 parameters (1 required) and no output schema, the description covers the domain, the search method, and the return shape (URL + match score)—essentially all a caller needs. The only gap is the lack of detail on how the match score is computed or ordered.

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?

With 0% schema description coverage, the description must compensate. It usefully explains that query means words matched against URL paths, giving meaning to an otherwise bare string parameter. However, the limit parameter is never mentioned in the text, so it relies entirely on the schema's default/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?

States a specific verb and resource ('Find pages on blvigil.com'), the search field ('by words in their URL path'), the method ('sitemap search'), and the output ('Returns URLs with a match score'). This clearly distinguishes it from sibling read_page (fetch one known page) and site_info (site metadata) without needing to open either 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?

The 'sitemap search' qualifier and the blvigil.com scoping imply it is for broad keyword-based lookup across the site's pages. However, it never names alternatives or states when NOT to use it (e.g., 'for a known URL, use read_page instead'), so usage guidance is implied rather than explicit.

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