lb_search_cancel

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

Annotations already indicate this is not read-only and not destructive, so the description's 'Cancel' action is consistent. The word 'active' adds a useful scoping hint that cancelling an inactive session may not be valid, but the description provides no further behavioral details such as side effects, idempotency, or error behavior.

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 redundant words. Every part contributes to stating the tool's core action.

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 simple one-parameter tool, a one-sentence description can almost suffice, but there is no output schema and no guidance on error cases like invalid or already-finished sessions. The description is minimally viable but leaves minor gaps that an agent might need filled for reliable invocation.

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 0% schema description coverage, the description carries the burden of explaining search_id but does not explain what it is, where it comes from, or how it relates to search sessions. The parameter name is somewhat self-explanatory, but the description adds no meaning beyond the bare schema definition.

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 ('Cancel') and resource ('an active search session'), making the tool's purpose immediately clear. It is easily distinguishable from sibling tools like lb_search_start, lb_search_read, and lb_search_sessions.

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 phrase 'active search session' gives an implicit condition for use: the session must exist and be active. However, there is no explicit comparison with alternatives, no when-not guidance, and no mention of how to obtain a valid search_id.

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