nop_method

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

No annotations provided, but description details that original is never modified, patched copy written to dst, type graph preserved, and version behavior (v2.8.0 returns status, v2.8.1 lands round-trip). Full disclosure of effects.

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 mostly concise with a clear structure, but includes some tangential references (RE-AI output directory, MainWindow.cs) that add minor clutter.

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 mentions return status and schema_for_replay, and covers type graph invariants. For a 4-param tool with clear use case, it is sufficiently complete.

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 0%, but the description's Args section adds key details: method_fqn format, dst must differ from path, confirm_legal as audit trail. Fully compensates for missing schema descriptions.

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 'Replace a method body with a NOP-sled (return default)', which is a specific verb and resource. It distinguishes from sibling tools like replace_method_body by specifying the NOP replacement.

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?

Provides a concrete use case (stubbing store/license/telemetry gates) and notes that dst must differ from path. However, it does not explicitly compare with sibling tools or state when not to use.

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