Enumerate

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is largely covered. The description adds one genuine piece of context not in annotations – that arbitrary host commands are blocked – but says nothing about the mutating bulk behavior, failure modes, or job/phase semantics referenced by the parameters.

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 short sentences with no padding, and the prohibition is stated up front. However the brevity is under-specification rather than disciplined concision for an 11-parameter tool with multiple modes.

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?

With 11 parameters, background jobs, phased push phases, and output schema richness, the description omits everything an agent needs to choose and drive this tool, including how it differs from the many rm_git_* siblings. An output schema exists, so return values are not its job, but the operational model is entirely absent.

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% and each parameter (phase, job_id, auto_start, target_project, run_precommit) is documented inline, so the baseline is 3. The description adds nothing to parameters, and notably never explains the missing action selector that the parameter docs repeatedly reference.

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?

"Enumerate (rm_git)" only restates the name, and "Typed bulk Git operations" names a category rather than a specific verb+resource. The many siblings (rm_git_status, rm_git_raw, rm_git_commit, rm_git_push, rm_git_phased_push) mean an agent cannot tell what this tool uniquely does or how it relates to those single-action tools.

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 mention of when to prefer this over the action-specific siblings, and no prerequisites. "Arbitrary host commands are prohibited" is a constraint, not a usage rule, so the agent is left to infer everything.

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