search.next_data

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

No annotations provided, so the description carries the full burden. It does not disclose whether this is a read-only operation (searching memory), what happens if no match is found, whether it advances some internal cursor, or what the return format looks like. The description is too minimal to inform an agent about behavioral traits like side effects or state changes.

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, short sentence with no wasted words. It is front-loaded and appropriate in length for a tool whose name already conveys purpose. However, it could pack slightly more meaning (e.g., mentioning hex format) without loss of conciseness.

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?

Given 3 required parameters, no annotations, no output schema, and many sibling search tools, this description is insufficient. An agent would need to guess that data_hex is hex-encoded bytes, that start might be a memory address or label, and that the tool returns the next match after a given point. Critical context about return format, error cases, and relationship to search.data is missing.

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%, so the description must compensate. It mentions 'data/byte-pattern' which maps to 'data_hex', but does not clarify that start can be either an integer address or a string (e.g., symbol name), nor does it explain the role of session_id (required for context). Two of three parameters lack any semantic context in the description.

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 'Find next data/byte-pattern match' gives a clear verb (find) and resource (data/byte-pattern match). It distinguishes from siblings like search.next_text and search.next_constant, which are for text and constant patterns respectively, but does not explain that it's for hex byte sequences specifically, which is implicit from the parameter name 'data_hex'.

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?

No explicit guidance on when to use this vs other search tools like search.data, search.next_text, or search.all_data. The description does not mention that this is a paginated/next-match variant of search.data, nor does it explain that it requires an ongoing session context (session_id). Usage is only implied by the tool name and schema.

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