git-observer

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly advertises 'read-only', which tells the agent there are no mutating side effects. However, it does not mention other behavioral traits such as whether it requires being inside a git repository, how it handles errors, or that the command parameter selects the specific operation.

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?

A single, front-loaded sentence conveys the core purpose with zero wasted words. It is appropriately sized for the tool's simplicity.

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?

The tool is simple, the schema fully documents all five parameters with descriptions, and an output schema exists so return values do not need explanation. The only notable gap is the lack of guidance about which sibling to choose for git operations, but that is covered more under usage guidelines than completeness.

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning about the parameters beyond what the schema already provides, and it does not clarify interactions between command and the optional parameters beyond what is in the schema.

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?

Description names a specific resource ('git status, log, and diff information') and a key attribute ('read-only'), making the tool's function clear. It does not explicitly contrast with siblings like terminal-runner, but the read-only scope and observer name strongly imply a safe inspection role.

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: when the agent needs read-only git status, log, or diff information. It provides no explicit guidance on when not to use it or how it compares to terminal-runner for executing git commands, leaving the routing decision partially to inference.

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