pull_source_control

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

Discloses that force=true permanently discards local changes and cannot be undone, which adds context beyond the destructiveHint annotation. Normal pull behavior could be elaborated.

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 concise sentences with no fluff. The critical warning is separated and front-loaded for emphasis.

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?

Lacks details about normal pull behavior (e.g., merge process, resulting state). No output schema, so more context would help. Prerequisite and destructive flag are covered.

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?

Both parameters have schema descriptions (100% coverage), so the description adds no new information beyond repeating the force warning. Baseline of 3 is appropriate.

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 uses the verb 'pull' and specifies the resource 'source-control repository', clearly differentiating from sibling tools that focus on workflows, users, and projects. It also mentions the prerequisite feature configuration.

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?

Explicitly states the requirement for the Source Control feature and warns that force=true is destructive and irreversible. Does not mention alternatives or when not to use, but the context is sufficient.

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