page_search

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

No annotations are provided, so the description carries the transparency burden. It discloses the tool reads the most recent snapshot and returns specific fields (role, name, path), and explains the dependency on prior calls. However, it doesn't explicitly state side-effect safety (though 'search' implies read-only) or behavior when no snapshot exists.

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?

Three sentences, each serving a purpose: stating the action and target, describing return fields, and giving a prerequisite. No redundant information or filler.

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 tool's purpose, dependency, and return shape, which is especially useful given there is no output schema. It lacks error-case handling, but for a simple search tool with well-documented parameters, it is sufficiently complete.

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 input schema already provides full descriptions for both parameters (100% coverage), so the description doesn't need to add parameter details. It neither repeats nor contradicts the schema, but adds no extra semantic value beyond the schema.

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 uses a specific verb ('Search') and resource ('most recent smart_snapshot tree'), making the tool's function clear. It distinguishes itself from sibling tools like snapshot_index or get_node by focusing on keyword search over a snapshot.

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 explicitly states to call smart_snapshot or snapshot_diff first, establishing a clear prerequisite and usage order. It does not name alternative tools for other scenarios, but the guidance is sufficient for when to use this tool.

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