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 performs a sitemap search and returns match scores, which is useful context beyond the annotations, though it does not disclose deeper behavioral aspects like data freshness or whether the search hits a live site.

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 a single, front-loaded sentence with no filler. It states the core operation first and the return value second, making it both concise and well-structured.

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?

The description covers the main purpose and output adequately for a simple search tool, but it lacks explicit guidance on query construction, the effect of the limit parameter, and the interpretation of match scores. Since there is no output schema, these details would improve agent success, but the core call is still understandable.

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 for parameter meaning. It implies 'query' should contain words to match against the URL path, but it never explicitly mentions the 'limit' parameter, its default, or how the match score works. This partial hint is not sufficient compensation for the missing parameter documentation.

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 verb ('Find'), a specific resource ('pages on continuum.blacklabelbots.com'), and the matching method ('words in their URL path'). It also defines the output ('Returns URLs with a match score'), making the tool's purpose unmistakable and implicitly distinct from siblings read_page and site_info.

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 provides clear context: use this tool to locate pages by URL path words rather than to read page content or get site metadata. It does not explicitly name alternatives or give when-not-to-use criteria, but the purpose is clear enough for an agent to select it appropriately.

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