GetTransport

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

No annotations provided, so description carries full burden. It declares read-only behavior via '[read-only]', which is valuable. However, it does not disclose other traits like required authorizations, rate limits, or what happens if transport_number is invalid. Basic transparency is achieved but not exhaustive.

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, front-loaded with key behavioral hint '[read-only]'. Every word contributes meaning without redundancy. Highly efficient and clear.

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?

No output schema exists, but description adequately conveys what the tool returns (metadata, objects, status). It covers the essential aspects for an agent to understand the purpose. Could be slightly improved by noting that it returns full transport details or listing example returned fields, but sufficient for correct 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?

Input schema provides 100% coverage with clear descriptions for all three parameters (transport_number, include_objects, include_tasks). The description does not add any additional semantic value beyond the schema, so baseline score of 3 is appropriate.

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 action (Retrieve), resource (ABAP transport request), and scope (including metadata, objects, status). Distinguishes itself from sibling tools like CreateTransport, ListTransports, and DeleteTransport by focusing on retrieval.

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?

Starts with '[read-only]' indicating it is for querying only, which helps set context. However, it does not explicitly mention when to use this over alternate retrieval tools like ListTransports, nor does it mention when not to use it. Lacks explicit alternatives or exclusion criteria.

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