gdb_source_window

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

With no annotations, the description carries full burden. It explains what is dumped but does not disclose side effects, whether it modifies GDB state, or if it pauses execution (beyond the pause_first parameter). Important behavioral traits are missing.

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?

The description is front-loaded with the purpose and then details what is dumped and parameter explanations. It is fairly concise but the Chinese phrase may reduce clarity for some agents. No redundant information.

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 complexity (memory dumping for exploit debugging), the description covers the parameters and output but lacks details on error conditions, required GDB state, or the exact return format (though output schema is mentioned). Annotations are absent, so more context would be beneficial.

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?

The description adds significant meaning to all five parameters, given 0% schema coverage. It defines source_chunk, source_size, before, after, and pause_first with specific roles, such as 'source_size: source 实际 chunk 大小，通常 chunk_sz & ~7，例如 0x40.'

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 states it views overflow-related windows around the SLPParseSrvUrl source chunk and dumps memory before/after the source chunk and the next chunk header. The verb 'view' is clear, but the Chinese phrase may cause ambiguity. It distinguishes from siblings by focusing on heap overflow exploitation, though not explicitly differentiating.

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 provides no guidance on when to use this tool versus alternatives like gdb_memory or heap_chunk_bin. It lacks context on prerequisites or scenarios where it is appropriate.

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