check_gitignore

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

With no annotations provided, the description carries the full burden and does so well: it discloses the underlying commands (git check-ignore, git ls-files, git log --all), the read-only guarantee ('no content is read, no history is rewritten'), the name-only matching scope, and the environmental prerequisite (git on PATH). That is exactly the behavioral context an agent needs before invoking it.

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 single dense paragraph is front-loaded with the scoping question, then works through verdicts, mechanism, safety guarantees, and prerequisites in a logical order with no filler. The trailing 'path: folder inside the repository to check.' line is tacked on awkwardly rather than integrated, which costs a point.

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-value shape need not be explained, and the description covers everything else: what is checked, which files are excluded, what the possible outcomes are, what side effects are absent, and what runtime dependency must exist. Nothing an agent needs in order to call this correctly is missing.

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 0% for the single parameter, but the description compensates by explaining that path is 'folder inside the repository to check', which clarifies it is scoped to the repo rather than an arbitrary filesystem path. It does not restate the default of '.', but the added meaning is sufficient for a one-parameter tool.

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 opens with a precise framing question and then names the exact resource set (.env/.env.* files, templates excluded) and the three verdicts it returns (ignored, tracked, present in any commit). It also calls out the history-deleted case and the ignored-template flag, which no sibling (env_overview, validate_env) covers, so an agent can tell it apart without reading schemas.

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?

The use case is strongly implied by the framing question 'Is each real env file safe from git?', which tells an agent this is the git-hygiene check. However, no sibling is named and there is no explicit 'use this instead of env_overview/validate_env when X' routing guidance, so the selection logic must be inferred from the sibling names alone.

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