find

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

No annotations exist, so the description carries the full burden. It conveys one useful behavioral fact — that searching operates over a stored/cached page inventory rather than the live page — but says nothing about read-only nature, staleness, pagination, or the shape of the result, and the sentence is cut off.

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?

A single truncated fragment ending in an ellipsis, prefixed with an unexplained 'TOOL 2' label. It is neither complete nor front-loaded with actionable content.

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 14-parameter, zero-required search tool with no annotations and no output schema, the description is far too thin: it omits result shape, empty/no-match behavior, and the meaning of the untagged filter parameters.

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 14 parameters at 71% schema coverage, several parameters (role, limit, query, tabId) have no schema description at all, and the description adds zero parameter meaning. Since coverage is below the 80% threshold, the description should compensate and does not.

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 names a verb (search) and resource (stored page inventory) and hints at the return payload ('WHERE and WHAT the hit is: its own role/name/attributes/state'). However it is truncated mid-sentence and gives no differentiation from siblings like page_slice or act, so an agent cannot confidently tell it apart.

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?

'TOOL 2' implies a pipeline position, but the description never states when to prefer this over page_slice, browse, or act, nor any preconditions (e.g. that an inventory must already be captured). No when-to-use or when-not guidance is present.

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