GetTransport

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

The description only includes '[read-only]' indicating no side effects, but no annotations are provided. It does not disclose handling of missing transports, authorization requirements, or error behaviors. The schema note about ECC vs S/4 behavior is not in the description.

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 with clear structure, front-loaded with '[read-only]'. No unnecessary words; every part adds value.

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 and no information about the return structure or error cases. The description lacks context about when to use this tool versus ListTransports, which is a crucial sibling. Incomplete for a read tool with potentially complex results.

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 coverage is 100%, so the schema fully documents all parameters. The description adds no extra meaning beyond the schema. 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 states the tool retrieves ABAP transport request information, specifying metadata, objects, and status. It uses a specific verb ('retrieve') and resource ('transport request'), distinguishing it from sibling list tools like ListTransports.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention prerequisites, when not to use, or alternative tools like ListTransports. The '[read-only]' flag is a property, not usage guidance.

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