Push abapGit Repository

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

Annotations already indicate destructiveHint=true and readOnlyHint=false; description adds context about 'confirmed staged', implying a safe state before destructive action. However, it does not explain consequences like overwriting remote or rollback possibilities.

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?

Single sentence is concise but lacks structure. No front-loading of key info beyond the basic action. Could be more informative without becoming verbose.

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 11 parameters, 5 required, and no parameter descriptions in schema or description, the tool is severely underspecified. The description omits output schema details and usage flows, making it incomplete for reliable agent 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?

With 0% schema description coverage, the description must compensate, but it mentions no parameters. The meaning of systemId, repositoryId, stageId, comment, confirmation, etc. is left entirely to the schema names, which is insufficient for an agent.

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 clearly specifies the verb 'Push', resource 'abapGit snapshot', and condition 'confirmed staged'. This differentiates from sibling tools like sap.git.stage (staging) and sap.git.pull (pulling).

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?

Implies use after staging and confirmation ('confirmed staged'), but provides no explicit guidance on when to use vs. alternatives (e.g., sap.git.pull) or prerequisites. Lacks clear when-not-to-use instructions.

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