jar_edit_class_constants

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

No annotations are provided, so the description carries the full behavioral burden. 'Edit' implies mutation, but it doesn't say whether the change is in-place on disk, scoped to an open session, reversible, or what happens if no occurrence matches - all critical for a bytecode-mutating tool.

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?

A single front-loaded sentence with no filler, clearly stating verb and target. It is arguably undersized for a 5-parameter mutation tool, but nothing in it is wasted.

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 a mutation tool with no annotations, no output schema, and a nested `replacements` object, the description omits too much: session requirements (session_id is required), failure behavior, and how the bytecode rewrite is applied. The agent cannot call this confidently.

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 description coverage is 100%, so the schema itself documents all five parameters, establishing a baseline of 3. The description adds nothing about the semantics of `replacements` (old_value -> new_value mapping), `occurrence` indexing behavior, or `value_type` hints.

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?

Specific verb and resource: 'Edit numeric constants in .class file bytecode.' This is distinguishable in principle from siblings like jar_edit_constant_pool and jar_hex_edit, but the description never explicitly contrasts itself with them, leaving the agent to infer which editing tool to pick.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as jar_edit_constant_pool or jar_hex_edit. The agent gets no routing help among several overlapping jar-editing tools.

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