task_reverse_engineer

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

The description mentions 'real-time progress', which hints at a streaming or long-running behavior. With no annotations, this adds some value, but it does not disclose other traits like whether the tool is read-only, destructive, or what happens with large inputs.

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 a single, focused sentence that conveys the core purpose and a key feature. No unnecessary words.

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 no output schema, the description lacks information about return values or output format. It also does not mention how the tool integrates with the module context or what the 'reverse engineering' produces (e.g., diagram, analysis). The 3 parameters are described in schema, but completeness suffers from missing output details.

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 coverage is 100% with parameter descriptions provided. The description adds no additional meaning beyond the schema, so it meets the baseline of 3.

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 clearly states the tool performs reverse engineering of a module with real-time progress. The verb 'reverse engineer' and resource 'module' are explicit. However, it does not differentiate from siblings like 'reverse_engineer_module' or 'task_reverse_engineer_async', which could cause confusion.

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 its alternatives. There is no mention of prerequisites, typical scenarios, or exclusions, leaving the agent without context for selection.

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