sap_call_function

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Call') but doesn't describe what happens during execution—such as whether it requires authentication, how errors are handled, if it's idempotent, or what the typical response format is. For a tool that likely interacts with external systems, this lack of behavioral context is a significant gap.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and target, making it easy to parse. Every part of the sentence earns its place by conveying essential information concisely.

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 complexity of calling OData functions (involving external systems, parameters, and potential side effects), the description is insufficient. There are no annotations to cover behavioral aspects, no output schema to describe return values, and the description lacks context on usage, prerequisites, or error handling. This leaves significant gaps for an agent to use the tool effectively.

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 schema description coverage is 100%, with clear descriptions for all parameters (serviceName, functionName, parameters). The description adds no additional semantic information beyond what's in the schema, such as examples of valid service names or how parameters map to OData functions. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema does the heavy lifting.

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 ('Call') and target ('an OData function import'), which is specific and unambiguous. It distinguishes this tool from siblings like sap_create_entity or sap_query_entity_set by focusing on function calls rather than entity operations. However, it doesn't explicitly differentiate from all siblings (e.g., sap_get_service_metadata might also involve OData services).

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a connection via sap_connect), typical use cases for OData functions, or when to choose this over other SAP tools like sap_query_entity_set. Without such context, the agent must infer usage from the tool name alone.

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