redefine_classes

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

No annotations provided, but description details the scan, match, redefine process, and return values. It discloses that it only works with Java debug sessions. Could mention limitations of JDI class redefinition (e.g., structural changes) but still informative.

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?

Three concise sentences with no wasted words. First sentence states the action, second explains the process and return, third adds a prerequisite. Front-loaded and efficient.

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?

Covers the core workflow, return values, and prerequisite. No output schema, but return values are described. Could elaborate on error cases or side effects, but sufficient for common usage.

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?

Adds value for sinceTimestamp by explaining its purpose and usage. classesDir schema description is adequate. sessionId lacks description in both schema and description, but the tool's context implies it comes from a debug session. Schema coverage is 67%.

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?

Clearly states it hot-swaps changed Java classes into a running JVM by scanning a directory and redefining classes. The verb 'redefine' and resource 'classes' are specific. Sibling tools are debug-session management or execution control, making this tool distinct.

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?

Explicitly restricts usage to Java debug sessions and describes the incremental update pattern using sinceTimestamp. However, it does not explicitly state when to avoid using this tool or mention alternatives.

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