sap_session_start

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to reveal important traits such as whether the tool is idempotent, requires authentication, has side effects (e.g., creating a new session or modifying state), or what happens if the session already exists. The description is too sparse for a start operation that likely has significant behavioral implications.

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 is concise and front-loaded with the essential action. It avoids unnecessary words. While it could be slightly more informative, it is not verbose.

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 (2 params, no output schema), the description still leaves significant gaps. It does not explain the return value, potential errors, or the effect of starting a session. Users are left without context on how this tool fits into a session lifecycle or what to expect after invocation.

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 both parameters already described in the schema. The description's mention of 'by session ID' adds no additional meaning beyond the schema's parameter description for sessionId. It does not clarify the purpose or format of vaultNonce beyond the schema. Thus, the description provides no incremental value for parameter understanding.

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 ('Start') and the resource ('high-level SDK session'), with the method ('by session ID'). It distinguishes from sibling tools like sap_fetch_session and sap_session_status, which are retrieval or status checks. However, it could be more explicit about what a 'high-level SDK session' entails to avoid ambiguity.

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. There is no mention of prerequisites, such as whether a session ID must already exist, or scenarios where starting a session is appropriate. Sibling tools like sap_session_read_latest and sap_session_status are not differentiated in terms of use cases.

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