list_user_transports

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

No annotations are provided, so the description must cover all behavioral aspects. It indicates the tool lists modifiable requests (read-only) and returns specific fields, but does not disclose permission requirements, scope limitations (e.g., what 'modifiable' means), or potential side effects (e.g., network calls). The description is adequate but not thorough.

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 a single sentence that conveys the essential information: action, resource scope, and return fields. It is front-loaded with the verb and resource, making it efficient and easy to parse.

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's simplicity (one optional parameter, no output schema, no nested objects), the description covers the main aspects: purpose, scope, and return fields. However, it does not define 'modifiable' or explain if there are any limits on the number of transports returned. Still, it is mostly complete for a straightforward list tool.

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?

The input schema has 100% description coverage for its single optional parameter (system_id). The tool description adds no additional meaning beyond the schema's description. 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?

The description clearly states the action ('List'), resource ('modifiable transport requests for the current SAP user'), and specific return fields (TR number, type, status, date, description). It distinguishes itself from sibling tools like 'get_transport' (single transport) and 'create_transport' (create vs list).

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 listing user's modifiable transports but does not explicitly state when to use this tool versus siblings like 'get_transport' for a specific transport or 'list_traces' for traces. No guidance on when to avoid or prerequisites are provided.

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