git_status

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

No annotations are provided, so the description carries the full burden. It does disclose the important scoping behavior — the tool acts on the 'active repository' with no repo argument — and 'Show' implies a non-mutating read, but it says nothing about output detail level, untracked-file handling, or whether the working tree must be clean.

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?

One sentence, front-loaded with the verb and resource, and every phrase (branch status, working-tree status, active repository) adds information. Nothing to trim.

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?

For a zero-parameter read tool with no output schema, the description covers what is inspected and what scope it applies to. The only real gap is what the returned status contains (ahead/behind counts, staged vs unstaged, untracked files), which an agent may want to know before parsing the result.

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?

The schema has zero parameters, so the baseline is 4. The description correctly implies no arguments are needed by anchoring the tool to the 'active repository', which explains why the input object is empty.

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?

Specific verb plus resource: 'Show Git branch and working-tree status', scoped to 'the active repository'. It is clearly distinct from siblings like git_diff, list_branches, or list_commits, though it never names them explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the read-only inspection step before diffing or committing, but the description offers no when-to-use framing or mention of alternatives such as git_diff for actual change content.

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