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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered; the description reinforces it with 'Changes nothing.' It adds genuinely new behavioral context beyond annotations: drift respects .gitignore, drift is measured against the current commit, and unexpected drift may signal compromise.

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 core sentence is front-loaded with a colon-delimited enumeration of outputs, and the second sentence adds an actionable warning. It is dense but not padded, though the first sentence is a long run-on that could be split for readability.

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?

There is no output schema, so the description must convey what comes back, and it does: repo, branch, commit, ahead/behind status, and drift broken into changed/new/deleted. An agent can predict the response shape and interpret an alarming result without further documentation.

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 coverage is 100%, so all three parameters (path, fetch, server) are already documented in the schema, making 3 the baseline. The description adds interpretive meaning to the drift concept but does not clarify the fetch or server parameters beyond what the schema states.

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 states a specific resource (a server folder) and enumerates exactly what is reported: repository, branch, commit, whether GitHub has newer commits, and live-file drift with change categories. It implicitly draws a clean line against the gh_* siblings by emphasizing server-side live files rather than GitHub API data.

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?

It supplies one useful trigger and a downstream routing hint ('Drift on a live shop nobody touched can be a hack: check it with malware_scan'), which is real guidance. However, it never says when to prefer this over gh_commits, git_deploy, or git_link, nor any when-not condition, so selection against siblings is left to inference.

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