Manage Transport Requests

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

The description adds behavioral context beyond annotations: it identifies 'assess_transport' as read-only and details confirmation requirements for destructive actions. This aligns with annotations (destructiveHint: true) and provides useful nuance.

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 (three sentences) and front-loaded with the main purpose. The third sentence adds specific guidelines. However, a structured list could improve readability given the many actions and confirmation formats.

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 24 parameters, no output schema, and no detailed action descriptions, the description is incomplete. It omits return values, behavior per action, and parameter semantics beyond confirmation, leaving significant gaps for the agent.

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?

With 0% schema coverage, the description fails to explain most parameters. Only the 'confirmation' parameter format is hinted. The 24 parameters (e.g., action, user, pgmid) are not described, forcing the agent to infer meaning from names or enums.

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 manages SAP transports and lists all major actions (list, inspect, assess, compare, create, release, delete, reassign, add objects, resolve). It distinguishes from sibling tools which focus on ABAP code inspection, not transport management.

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 provides specific confirmation formats for different actions (release/delete, owner/user, object), guiding usage. While it doesn't explicitly compare to alternatives, the sibling tools are unrelated to transport management, making the tool's context clear.

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