ida_get_pseudocode

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

No annotations provided, so description should compensate. It fails to disclose behavioral traits like side effects, permissions, or read-only nature. Minimal transparency beyond the basic action.

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?

Description is a single sentence, concise and front-loaded. However, it may be too brief to be maximally informative, losing points for missing content.

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 3 parameters with no schema descriptions and no annotations, the description is incomplete. It does not explain defaults or parameter roles. Output schema exists but does not justify the lack of parameter guidance.

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%. Description does not explain any of the three parameters (max_chars, scan_json, name_or_ea). It only vaguely implies name_or_ea via 'specified function', leaving parameter semantics entirely to the schema.

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?

Description states verb '获取' (get) and resource '反编译伪代码和地址' (decompiled pseudocode and address), specifying '指定函数' (specified function). This clearly identifies the tool's purpose and distinguishes it from siblings like ida_find_functions or ida_get_xrefs.

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?

Description implies usage when needing decompiled pseudocode for a function, but provides no guidance on when not to use or alternatives. Context is clear but exclusions are missing.

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