sap_connect

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Connect' implies establishing a session or authentication, but it doesn't describe what happens after connection (e.g., session persistence, authentication mechanism, error handling, or what 'connection' means in this context). For a tool with 7 parameters and no annotation coverage, this is inadequate.

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 gets straight to the point with zero wasted words. It's appropriately sized for a connection tool and front-loaded with the essential action, making it easy for an agent to parse quickly.

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 connecting to an SAP OData service (involving authentication, session management, etc.), no annotations, and no output schema, the description is insufficient. It doesn't explain what the connection enables, how long it lasts, error conditions, or what the tool returns. For a foundational tool in an SAP integration suite, this leaves critical gaps.

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 100%, so the schema already documents all 7 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema, meeting the baseline score of 3 for high schema coverage. No compensation is needed since schema coverage is complete.

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 'Connect to SAP OData service' clearly states the verb ('Connect') and resource ('SAP OData service'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'sap_disconnect' or 'sap_connection_status' that also relate to connection management, so it doesn't reach the highest score.

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, when this should be called before other SAP operations, or how it relates to siblings like 'sap_disconnect' or 'sap_connection_status'. This leaves the agent without context for proper tool selection.

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