lb_search_read

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds the pagination concept ('a page of results') but does not detail behavior like offset handling or session validity, which is expected for a read operation.

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?

Single sentence with a clear verb and object, no fluff. Front-loaded with the core purpose.

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?

Description is minimal; it does not explain how pagination works (e.g., using result_offset to get subsequent pages), what the response contains, or error conditions. With no output schema, the agent lacks guidance on return format. However, the tool is simple and the schema provides basic parameter constraints, so a 3 is appropriate.

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%, and the description provides no information about search_id, result_count, or result_offset beyond their names. The schema includes defaults and constraints, but the description does not add meaning to parameters or explain how they interact for pagination.

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?

States a specific verb (Read) and resource (results from an existing search session). Clearly distinguishes from siblings like lb_search_start and lb_search_sessions, which are about starting or listing 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?

Implies it must be used after a search session exists, but does not explicitly state when to use this over alternatives or any exclusions. No mention of alternative tools or when not to use it.

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