Maintain Status

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=false, and destructiveHint=false, so the safety posture is partly covered structurally. The description adds nothing beyond that — no mention of what the maintain action mutates (version bumps, tags), no note that force can delete an orphan local next-version tag, and no indication that install performs symlink/uv sync side effects. It does not contradict the annotations.

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?

Two very short sentences, but neither earns its place: the first is a name restatement and the second is filler boilerplate. Brevity here is under-specification rather than effective concision, since the front-loaded content conveys no actionable information.

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?

An output schema exists so return values need not be explained, and the schema carries parameter detail. But for a multi-action tool with 13 parameters and no required fields, the description omits the one thing only prose can supply — which action this invocation corresponds to and what each action does — leaving the agent to reverse-engineer behavior from parameter descriptions.

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 already documents all 13 parameters richly (including action-scoping notes like 'for maintain_status'). Per the rubric, a high-coverage schema sets the baseline at 3 even when the description contributes no parameter detail, which is the case here.

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 restates the tool name and title ('Maintain status') and pads it with a generic mission statement ('Core workspace organization, configuration, and maintenance') that could describe dozens of sibling tools. It never says what the tool actually does — the schema reveals it is an action dispatcher covering 'maintain', 'maintain_status', 'setup', 'template', and 'save', none of which the description mentions.

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 and no mention of alternatives such as rm_workspace_maintain, rm_gates_status, or rm_build_status. For a 13-parameter umbrella tool whose parameters select between five different operations, the absence of any routing instruction is a real gap, not merely a stylistic one.

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