SAPGit

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows it mutates and is destructive. The description adds that gCTS mutations are quarantined and abapGit mutations require write/Git gates, but it does not specify exactly which actions are quarantined, what 'gates' entail, or the scope of destruction — leaving meaningful behavioral gaps beyond the annotations.

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 description is a dense, jargon-heavy sentence fragment that is not front-loaded with the primary purpose. It prioritizes constraints over clarity.

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 destructive tool with 14 parameters and no output schema, the description is incomplete. It fails to outline which actions are available, the differences between backends, or the expected outcomes, leaving the agent under-informed.

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 86% schema description coverage, the schema already documents most parameters. The description adds little: it implies ROOT/** or * for allowedPackages but doesn't explain many action-specific parameters or their 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?

The description mentions 'Git reads and gated abapGit workflows' but doesn't clearly state the core action or distinguish this tool from siblings like SAPManage or SAPRead. The focus on gating constraints obscures the actual purpose.

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?

It describes constraints on mutations but doesn't say when an agent should choose this tool over SAPManage or SAPRead, nor provide any explicit usage scenarios or alternatives.

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