sap_rfc_call

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

With no annotations, the description bears full burden for behavioral disclosure. It mentions safety policy via environment variables but does not explain effects like mutation, rate limits, or error behavior. Critical details for responsible tool invocation are missing.

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 front-loaded and concise, with only three sentences. It avoids redundant details but could be better structured by separating usage, safety, and parameter hints. Slightly more content would improve clarity 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?

Despite having an output schema, the description is incomplete given the tool's complexity (10 parameters, potentially damaging effects). It fails to elaborate on return values, error handling, or parameter relationships, leaving significant gaps for an agent to infer.

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%. The description adds no meaning to any of the 10 parameters beyond the bare schema titles. An agent receives no guidance on how to populate import_params, tables, or other complex structures, making effective use difficult.

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 calls any RFC-enabled function module, with explicit parameters and outputs. It distinguishes from sibling tools like sap_describe_rfc (inspect/describe) and sap_search_rfc (search) by focusing on execution.

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 explicitly instructs the host LLM to first inspect/choose a function before calling this tool, providing clear context. However, it lacks explicit when-not-to-use or alternative constraints beyond implied safety enforcement.

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