Find in page snapshot

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

The readOnlyHint annotation already covers safety; the description adds that it returns matching lines with refs, which is helpful behavioral detail. No contradiction with annotations, and the cost note adds transparency.

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 concise sentences that pack in purpose, cost advantage, and return value. No wasted words, and the structure is direct and easy to parse.

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 is complete for the tool's purpose. It tells the agent when to use it, what it does, and why it's beneficial, without needing additional context. Missing output schema details are not required for correct usage.

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?

The schema descriptions cover each parameter fully (text, regex, context). The description does not add additional meaning beyond the schema, but no further clarification is needed, so a baseline score of 3 is appropriate.

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?

Clearly states the tool's function: search the current snapshot for text or regex and return matching lines with refs. It also highlights the cost benefit compared to reading the whole snapshot, effectively distinguishing it from snapshot retrieval tools.

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?

Explicitly mentions the primary use case (locating one element) and contrasts with the more expensive alternative (re-reading the whole snapshot). This gives clear guidance on when to use this tool over others.

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