Run SAP Transaction

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

Annotations indicate the tool is not read-only, not idempotent, and not destructive. The description adds that parameter values use a 'restricted injection-safe character set,' which provides security context. However, it does not explain other behavioral aspects such as side effects or authentication requirements.

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 consists of two succinct sentences with no redundant words. The first sentence delivers the core purpose, and the second adds an important security constraint.

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 4 parameters (2 required), no output schema, and moderate complexity, the description is insufficient. It does not mention return values (e.g., URL string or launch behavior), error conditions, or how the 'parameters' object should be constructed.

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%, so the description must compensate. It vaguely mentions parameter values using a restricted character set but does not explain the purpose or allowed values of 'connectionId', 'transactionCode', 'mode', or the 'parameters' object.

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's purpose: 'Build a validated SAP WebGUI transaction URL, or launch it with the local default browser.' This is a specific verb-resource combination that distinguishes it from sibling tools, which focus on ABAP development and analysis rather than executing transactions.

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 by stating the two modes ('url' or 'launch') but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or context-dependent choices.

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