list_symbols

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

With no annotations, the description carries the full burden and does disclose two useful traits: it is READ-ONLY and fast (r2/rizin, seconds, no Ghidra). It does not mention output size limits, truncation, or failure modes for invalid paths, so the behavioral picture is only partially filled in.

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?

Three short telegraphic fragments, front-loaded with what the tool is and what it returns. Nothing is padded, though the clipped style costs a little readability.

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-value documentation is unnecessary, and the description supplies the allowed kind values, the read-only guarantee, and the intended workflow position. Only minor gaps remain around path semantics and result limits.

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 kind parameter has no enum, so the description's explicit 'kind = functions | imports | strings' is the only source of allowed values and is essential. The path parameter is left unexplained, but its meaning is obvious.

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 concrete resource (symbol inventory via r2/rizin, no Ghidra, seconds) and enumerates the three kinds of symbols it can return. It also implicitly distinguishes itself from the heavier sibling decompile_function, though it doesn't contrast with analyze_binary or analyze_apk.

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?

"Gut für den ersten Überblick / um Ziele für decompile_function zu finden" gives an explicit first-pass recon role and names the natural follow-up tool. It stops short of stating when NOT to use it (e.g., when decompilation or full analysis is needed instead).

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