Switch abapGit Branch

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

The description adds minimal behavioral context beyond what annotations already provide. It mentions 'switch or create' but does not explain destructive implications (e.g., overwriting local changes) or authentication requirements. The annotations indicate destructiveHint=true, but the description lacks elaboration.

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 concise (one sentence) and front-loaded, but it is under-specified for a tool with five parameters and complex semantics. Every word is necessary, but the brevity undermines 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?

Given the tool's complexity (5 parameters, 4 required, no enums, output schema present), the description is too brief. It does not explain what 'confirmed' means, what the 'branch' parameter expects, or any additional context needed for correct invocation.

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 0%, meaning no parameter descriptions exist. The tool description does not mention or explain any of the five parameters (e.g., branch, systemId, confirmation, createBranch, repositoryId), failing to add meaning beyond the input 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?

The description clearly states the verb ('Switch or create') and the resource ('abapGit branch'), distinguishing it from sibling tools like 'sap.git.create' or 'sap.git.pull'. The qualifier 'confirmed' adds specificity.

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 usage for switching or creating a branch but provides no explicit guidance on when to use this tool versus alternatives. No exclusions or alternative recommendations are given.

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