Pull

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is largely covered. The description adds one genuinely useful behavioral constraint — arbitrary host commands are prohibited — which is relevant given the schema's free-form 'command' parameter, but it omits what a pull actually mutates and any auth/scope conditions.

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 filler, and the tool/name anchor is front-loaded. It is efficient, though the brevity is partly under-specification rather than disciplined concision.

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?

This is an 11-parameter multiplexed tool whose schema references distinct actions (status, cancel, raw, commit, phased_push) via job_id, command, phase, and the *_project fields. The description says nothing about that action dispatch model, the bulk/multi-repo behavior, or the threading option. An output schema exists so return values need no explanation, but the operational model is essentially undocumented.

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 every one of the 11 parameters is already documented inline (including action-specific fields like job_id, phase, and target_project). The description contributes no parameter meaning beyond that, so the baseline 3 applies.

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?

"Pull (rm_git)" restates the tool's own title, and the second sentence ("Typed bulk Git operations; arbitrary host commands are prohibited") describes the rm_git family posture rather than what this specific tool does. It never states that it fetches/merges changes into repositories, nor how it differs from rm_git_push, rm_git_raw, or repository_manager_pull_projects.

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?

No when-to-use guidance, no prerequisites, and no named alternatives among the many sibling Git/pull tools (rm_git_push, rm_git_raw, repository_manager_pull_project(s)). The only directing statement is a prohibition (no arbitrary host commands), which hints at choosing rm_git_raw vs this tool but is not framed as usage guidance.

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