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

No annotations exist, so the description carries the full burden. It discloses the operation is a lookup and that results include a match score, which is useful, but says nothing about permissions, throttling, pagination, or absence of side effects beyond the implied read nature.

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 sentences with zero filler; the purpose and behavior are front-loaded and the return hint is appended economically.

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 annotations and no output schema, the description covers enough to call the tool but leaves gaps: the 'limit' parameter is unexplained and the scope is limited to blvigil.com without clarifying coverage. Adequate but not complete for a search tool with an undocumented parameter.

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 explains the 'query' parameter reasonably ('words in their URL path') but never addresses 'limit' (default 20, max 50) or what a match score means, leaving one of two parameters entirely undocumented.

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+resource ('Find pages') and the matching mechanism ('by words in their URL path (sitemap search)'), which is concrete enough to distinguish it from read_page and site_info. It does not, however, explicitly name those siblings or contrast the modes, so it stops short of the top score.

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?

There is no when-to-use guidance and no mention of alternatives, even though read_page and site_info are obvious neighbors an agent must choose between. The '(sitemap search)' parenthetical implies the mechanism but not when to prefer this over fetching a page directly.

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