Delete SAP Transport

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

Annotations already indicate destructiveHint=true, so the description's mention of 'delete' aligns. The description adds the requirement for 'exact confirmation', which is a behavioral detail. However, it does not disclose potential side effects or prerequisites beyond confirmation.

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 very brief (only 5 words) and front-loaded. While concise, it sacrifices necessary detail, making it less informative for a tool with three required parameters and significant implications.

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 that this is a destructive operation with three required parameters, the description lacks essential context: what a transport is, prerequisites for deletion, and what happens post-deletion. Even with an output schema, the description is too sparse.

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?

The description does not explain any of the three parameters (systemId, transportNumber, confirmation) beyond hinting at confirmation. With schema description coverage at 0%, the description fails to add meaning to the parameters.

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 that the tool deletes an SAP Transport and requires 'exact confirmation'. It is distinct from sibling transport tools like sap.transport.create and sap.transport.release. However, it could be more specific about what constitutes a transport in this context.

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 provides a usage hint ('after exact confirmation') but does not give explicit guidance on when to use this tool versus alternatives like sap.transport.release or sap.transport.inspect. No when-not-to-use advice is present.

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