search.next_constant

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

With no annotations, the description must disclose behavioral traits. It only says 'Find next constant occurrence' without indicating whether the search is forward from 'start', if it modifies state, requires an open session, or what 'next' means. Critical behavior like direction, repeatability, and side effects are missing.

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 one sentence, but it is under-specified. True conciseness would include enough context to be useful. For a tool with three parameters and no schema descriptions, this brevity forces the agent to guess. The structure is front-loaded but incomplete.

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 the presence of many sibling search tools (search.next_text, search.all_constant, etc.), no output schema, and no annotations, the description leaves too many gaps. The agent cannot reliably understand the input semantics, return value, or how this tool integrates with other search operations. It is not complete enough to be used correctly without prior knowledge.

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 explain the three parameters. It does not: 'start', 'constant', and 'session_id' are unexplained. While 'constant' is hinted by the tool name, the meaning of 'start' (likely an address or position) and the role of 'session_id' are entirely absent. This is a significant gap.

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 constant occurrence.' clearly states the action (find) and the resource (constant occurrence). It distinguishes from sibling tools like search.next_text and search.next_data by specifying 'constant', but could be more explicit about what a constant is in this binary analysis context.

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 guidance on when to use this tool versus alternatives like search.all_constant or search.next_data. There is no mention of prerequisites, ordering constraints, or scenarios where this tool is preferred. The agent receives no decision support.

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