Start SAP Memory Session

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

Annotations indicate write operation (readOnlyHint=false) and nondestructive. Description adds security guidance: 'Store only intentionally encrypted payloads or public hashes; session and vault PDAs are visible on-chain metadata,' which warns about data visibility. This goes beyond annotations. No contradiction found.

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?

Two concise sentences plus a brief security note. Information is front-loaded with the primary action. Could be slightly more structured, but no unnecessary content.

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?

Output schema exists so return value is handled. For a session-start tool, additional context about lifecycle (e.g., subsequent tool usage or failure conditions) would be helpful but not strictly required. Adequate.

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 has 100% coverage of 2 parameters with descriptions. Description does not add extra meaning beyond the schema, such as format constraints or usage examples for vaultNonce. Baseline 3 is appropriate.

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?

Description clearly states 'Start a high-level SDK session by session ID' with a specific verb and resource. It includes 'SAP MCP context: Memory/session flow' which helps distinguish it from sibling tools like sap_open_vault_session, though the term 'high-level SDK session' could be more precise.

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?

Implied usage through context ('Memory/session flow'), but no explicit guidance on when to use this tool vs. alternatives like sap_open_vault_session. No 'when not to use' or prerequisite conditions are stated.

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