search_rop_gadgets

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it says nothing about whether the search is read-only, how results are ordered, or whether gadgets span multiple instructions. It also ignores session_id behavior entirely, leaving the agent unaware of the session-scoping model.

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?

Very short and front-loaded, with the core purpose in the first phrase. The brevity borders on under-specification, and the stray '( /R)' token adds noise without earning its place.

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?

An output schema exists so return values need not be explained, but for a 3-parameter tool with 0% schema coverage and no annotations, the description leaves critical gaps: the meaning of max_length, the role of session_id, and the expected shape/interpretation of the instructions list.

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% for three parameters, so the description must compensate and does not. The unlabeled example hints at the instructions array format but never names it, and max_length (default 5) and session_id are completely undocumented in both places.

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+resource combination (search for ROP gadgets) that is distinguishable from generic search siblings at a glance. However, the parenthetical '( /R)' is unexplained and the example is unlabeled, so the agent must guess whether it illustrates the instructions format or expected output. It does not explicitly differentiate itself from search_bytes or search_string.

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 versus search_bytes or search_string, which occupy similar semantic territory. There is no mention of prerequisites (e.g., whether an active session or loaded binary is required), even though a session_id parameter exists.

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