list_strings

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

No annotations are present, so the description must carry the full burden. It states the tool lists defined strings and supports case-insensitive filtering, but it does not disclose whether this is a read-only operation, potential performance implications, or what constitutes a 'defined string' (e.g., strings from analysis vs. runtime). Basic but adequate.

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?

Two sentences, front-loaded with the core action, no filler. Every word serves a purpose. The optional filter detail is placed after the main statement, which is logical.

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 tool's simplicity (one optional parameter, output schema exists), the description is largely complete. An agent can understand what the tool does and how to use the filter. Minor gap: it doesn't explicitly state the scope of 'defined strings' (e.g., all strings in the binary's string list vs. only select sections), but this is implied by the tool name.

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 compensates well by noting the filter is optional and case-insensitive. This adds meaning beyond the schema's bare parameter definition. However, it could additionally clarify whether wildcards or exact matching are supported.

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 'List all defined strings in the binary' uses a specific verb (list) and resource (strings), clearly distinguishing it from sibling tools like list_functions or list_structs. The optional filter is also mentioned, making the purpose very clear.

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 description implies usage for listing strings with optional filtering, but it does not explicitly state when to use this tool versus alternatives like search_text (which searches across multiple types) or list_imports. No exclusions or context about when not to use it are provided.

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