abap_transport

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

Annotations already mark the tool as not read-only and destructive. The description adds useful behavior beyond that: reads are always permitted, mutations are gated by write allowlists, and deletion is among the dangerous operations (echoing the request number to arm delete is covered in the schema). No contradiction with 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?

Two compact sentences with the operation list front-loaded and no filler. The write-allowlist constraint and release-tool routing each earn their place and are expressed economically.

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 an 8-operation tool with no output schema, the description does not say what each operation returns (e.g., whether 'check' returns a boolean, what 'list' returns, or what 'users' shows). It also leaves 'write allowlists' undefined. Parameter mappings are thorough, but response/behavior expectations remain partly implicit.

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 schema descriptions already cover all parameters in detail, including which operation each parameter is required for. The tool description adds value by enumerating the allowed operation values and disambiguating 'check' as 'does an object need a transport?', which is essential because the shown schema does not define an 'operation' property.

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 names a specific verb and resource ('Inspect and manage CTS transport requests') and enumerates the exact operations: list, show, check, users, create, addUser, setOwner, delete. It also clearly routes release work to a separate tool, abap_transport_release, which distinguishes it from a likely sibling.

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 gives clear operating context: reads are always allowed, mutating operations obey write allowlists, and release is not part of this tool. It does not exhaustively compare against all sibling tools like abap_read or abap_search, but the transport-request domain plus release exclusion is enough to guide selection in most cases.

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