git_remote_status

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description aligns with that. It adds meaningful behavioral context by disclosing that refresh=true performs a fetch first, which is a non-destructive side effect beyond what the annotations state.

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 sentences, with the core purpose front-loaded and the optional-refresh explanation following immediately. Every sentence adds value and there is no filler.

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 read-only status tool with no required parameters and no output schema, the description covers the main behavior and the one non-default option. It does not describe the exact return format, but the ahead/behind status is strongly implied by 'local-vs-remote branch state.'

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 input schema already documents all four parameters with 100% coverage, so the baseline applies. The description clarifies why refresh=true is useful (current remote state), but this largely restates the schema's refresh description rather than adding substantial new meaning.

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 a specific verb ('Read') and a precise object ('local-vs-remote branch state'), making the tool's function unmistakable. It also distinguishes the tool from siblings like git_status by focusing on the remote comparison rather than working-tree status.

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 description implies when to use the tool—whenever local branch state must be compared to remote state—and gives a concrete parameter-level guideline for refresh=true. However, it never names alternative tools or states when not to use this one, so selection guidance is only implied.

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