Manage abapGit

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

The description adds behavioral context beyond annotations by specifying the confirmation format for create ('PACKAGE:CANONICAL_URL') and that other mutations use repositoryId. This aligns with the destructiveHint annotation and provides practical usage details.

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 two sentences long, front-loading the action list for quick understanding. Every word adds value, with no redundancy or fluff.

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 19 parameters, destructive nature, and no output schema, the description minimally covers the tool's usage. It lacks details about each action's effects, parameter combinations, or expected return values, leaving significant gaps for a complex tool.

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 0% schema description coverage, the description does not explain individual parameters. While it mentions confirmation and repositoryId, it does not detail their syntax, constraints, or relationship to other parameters, leaving the agent to infer from parameter names.

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 lists a comprehensive set of actions (list, inspect, create, pull, etc.) on abapGit repositories, clearly defining the tool's scope. It distinguishes from sibling tools by focusing specifically on repository management, which is unique among the listed siblings.

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 states that credentials come only from the secret store, providing a clear prerequisite for usage. However, it does not explicitly state when not to use this tool or suggest alternatives for similar tasks, leaving some ambiguity.

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