Reverse Engineer Module (Async)

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

No annotations provided, so the description must fully disclose behavior. It mentions 'async' which is already in the name, but does not explain side effects, idempotency, rate limits, or return type. The description adds minimal value beyond the tool name.

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?

Single sentence succinctly states the tool's purpose. It is front-loaded with the key action. However, being too short, it omits important details about async behavior and output, which slightly reduces effectiveness.

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?

For an async tool, the description fails to explain what the tool returns (e.g., task ID, progress URL). No output schema exists, so the description should describe the return value. It mentions extracting contracts and generating docs but does not clarify how the agent gets these results.

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?

Input schema has 100% coverage with descriptions for all 3 parameters. The tool description repeats what is already in the schema (e.g., code snippet, language, context) without adding new semantic meaning or usage hints. Baseline 3 is appropriate since schema handles parameters well.

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 clearly states it is an asynchronous reverse engineering tool for modules, extracting contracts, dependencies, and generating documentation. It distinguishes from siblings like reverse_engineer_module and task_reverse_engineer by adding 'async' in name and description, but does not elaborate on what asynchronous means in practice.

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?

No guidance on when to use this async version versus the synchronous alternatives. The description does not mention use cases, prerequisites, or situations where this tool is preferred.

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