decompile_to_file

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

Discloses that each function requires a separate IDA decompile call and that 'all' uses paginated queries to avoid blocking. No annotations are provided, so the description carries the full burden, which it does adequately.

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 well-structured sentences with a clear imperative and a critical warning in all caps. Every sentence adds value with no fluff.

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?

Covers the core action, performance implications, and a usage tip for large binaries. With high schema coverage and an output schema present, only minor details like file naming or overwrite behavior are omitted, which is acceptable.

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 covers all parameters (100% coverage), so baseline is 3. The description adds context about 'all' using paginated queries and the importance of checking function count, but does not introduce new details about other parameters.

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?

Clearly states the verb 'decompile functions' and the resource 'save results directly to files on disk', distinguishing it from the sibling 'decompile' tool which likely outputs to screen or memory. Provides additional context about performance implications.

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?

Explicitly advises to check function count with list_funcs before using 'all' on large binaries, and warns about time costs. However, does not compare to other tools like 'decompile' or specify when not to use the tool.

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