Inspect SAP Transport

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no additional behavioral context beyond stating 'Read,' so it does not enhance transparency beyond the 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?

The description is concise (one sentence), but it is too brief and lacks structure. It could be expanded slightly to include parameter or behavioral details without losing conciseness.

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 the tool has 6 parameters (2 required) and an output schema, the description is insufficient. It does not explain the purpose of parameters or what the output contains, relying on the output schema for return values. The description should at least mention key parameters like view and transportNumber.

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 0%, yet the description provides no explanation of any parameters. It vaguely hints at the 'view' parameter with 'details or objects' but fails to describe the other five parameters (systemId, transportNumber, limit, startIndex, includeObjects). The description adds almost no value beyond the property names in the schema.

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 the tool reads details or objects for a single transport request, distinguishing it from sibling tools like sap.transport.list (which lists multiple transports) and sap.transport.compare (compares transports). However, it does not explicitly differentiate or mention alternatives.

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 implies usage for inspecting a specific transport but provides no explicit guidance on when to use this tool over alternatives like sap.transport.list or sap.transport.compare. No when-not-to-use or prerequisites are mentioned.

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