Configure git integration

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

Discloses that no secrets are stored and that push uses the machine's own credentials, adding important behavioral context beyond annotations. Aligns with idempotentHint.

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 concise sentences that front-load the purpose and add necessary behavioral details without verbosity.

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?

Covers main purpose and key behavioral traits but lacks parameter-level detail and does not mention idempotent nature (though annotated). Adequate but could be more thorough given parameter count.

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?

With only 17% schema description coverage, the description explains key concepts (credential handling, codeLocation) but fails to describe individual parameters like branch, remote, enabled, messagePrefix. Agent cannot fully interpret parameter semantics.

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?

Clearly states the verb ('Enable/configure') and the resource ('per-project git integration'). Differentiates from siblings like 'get_git_config' and 'commit_feature' by focusing on setup and configuration.

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?

Provides context for when to use (setting up git integration) and mentions prerequisite ('Set codeLocation in project config'). Does not explicitly list alternatives but implies distinction from similar tools.

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