windbg_find_vtable

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It explains the check-and-resolve behavior, but does not mention whether the tool reads memory directly, what happens if the address is not a vtable, whether symbols must be loaded, or any potential side effects. This is a significant gap for a tool without annotation support.

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 two sentences with no redundant language. It front-loads the action and purpose, then adds the use case. Every word earns its place.

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?

The tool is simple (one parameter, no output schema), and the description covers the core purpose and a use case. However, it does not specify the exact return format or behavior for non-vtable addresses, which would help an agent fully anticipate the tool's output. Given the lack of annotations and output schema, more detail could be justified.

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 schema already describes the 'address' parameter as 'Address that may contain a vtable pointer' with 100% coverage. The description reinforces this by explaining the tool's purpose with that address, but does not add format requirements or additional nuances, so a baseline score of 3 is appropriate.

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 uses a specific verb ('Check') and clearly states the resource ('an address contains a vtable pointer') and the expected outcome ('resolve it to a symbol + disassembly'). This distinguishes it from the sibling windbg_find_vtable_owner, which focuses on ownership rather than symbol resolution.

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 a clear use context: 'Useful for type confusion / UAF analysis.' However, it does not explicitly state when to use this tool over similar windbg tools (e.g., windbg_find_vtable_owner) or provide exclusions, so the guidance is implied rather than explicit.

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