osd_reweight

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

Despite having no annotations, the description discloses the write nature with '[WRITE]', risk level 'medium', reversibility ('Reversible → prior weight'), and the dry-run preview behavior. It goes beyond the schema and gives the agent a clear picture of side effects and safety.

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 tightly structured and front-loaded: starting with tags, then a one-sentence summary, reversibility note, dry-run note, and a clean Args list. Every sentence adds value and there is no redundancy.

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 4-parameter mutation tool with no output schema and no annotations, the description covers parameters, side effects, reversibility, and usage examples. It lacks explicit prerequisites or error conditions, but the essential information for calling the tool correctly is present.

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?

The schema provides only types and defaults with zero property descriptions, so the description must compensate. The 'Args' section fully explains each parameter: osd_id source, weight range and drain semantics, dry_run behavior, and target configuration. This is meaningful beyond the schema.

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 a specific action: 'Set an OSD's reweight (0.0 drains it)' with the target resource identified. It also includes the key effect and reversal, making it distinct from sibling tools like osd_mark_out or osd_purge.

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 implies usage context through dry_run and the drain behavior, but it does not explicitly state when to choose this over alternatives like osd_mark_out or osd_purge. There is no direct when-to-use or when-not-to-use guidance, though the '0.0 drains it' hints at a common scenario.

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