GetTransport

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

No annotations are supplied, so the description carries the burden, and it does declare '[read-only]' plus the scope of retrieved data — useful safety context. It stops short of permission requirements, whether the transport must be released/modifiable, or error behavior for an invalid transport number.

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?

One front-loaded sentence with the read-only marker up front and zero padding. It is efficient, though the sentence could have used a second clause to route the agent away from the overlapping siblings.

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 a simple read tool with three fully documented parameters and no output schema, the description adequately signals the shape of the return (metadata, objects, status) and the read-only nature. Only routing against sibling transport tools is missing.

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 100%, so transport_number, include_tasks and include_objects are already fully documented, including the 'not a task' caveat. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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?

Specific verb+resource: 'Retrieve ABAP transport request information' with a clear enumeration of what comes back (metadata, included objects, status). It does not, however, differentiate itself from near-siblings like ReadTransportObjects or ListTransports, so an agent must infer the boundary.

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?

No when-to-use guidance, no prerequisites, and no alternatives named despite several transport-related siblings (ListTransports, ReadTransportObjects, ReadTransportActionLog, CreateTransport). Usage is only implied by the noun 'transport request'.

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