Read Latest SAP Session Entries

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

The description claims 'Read latest entries', implying a read-only operation, but annotations set readOnlyHint=false, indicating it may modify state. This contradicts the behavioral hint. Additionally, the description lacks details on side effects or authorization needs.

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 two sentences, concise and front-loaded with the core action. The second sentence adds context but is slightly tangential, earning a 4 rating.

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?

The tool has an output schema, so return values are covered. However, the behavioral contradiction (read vs. potentially write) undermines completeness. The description omits important behavioral context despite the existence of annotations.

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 input schema already describes the sessionId parameter with 100% coverage. The description adds no further semantic meaning beyond what the schema provides, so a baseline of 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?

The description clearly states the tool reads latest entries from a session ID, with a specific verb ('Read') and resource ('entries from a high-level SDK session ID'). It distinguishes from siblings like sap_session_status (checks status) and sap_session_start (starts session).

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?

Provides context about the SAP MCP memory/session flow and advice on what data to store. However, it does not explicitly state when not to use this tool or suggest alternatives among siblings.

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