sap_session_status

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It states the tool fetches status but omits critical details: whether it is read-only, requires authentication, idempotency, error conditions (e.g., missing session ID), or side effects. The minimal description fails to inform the agent about safety or constraints.

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 with no redundancy. It is front-loaded with the action and resource. However, it could incorporate more critical information without losing conciseness.

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?

For a simple fetch tool with one parameter and no output schema, the description is minimally adequate. It lacks context about return format, whether the session ID is required (despite required parameters being 0), and any behavioral or safety information. With no annotations, more completeness is expected.

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%, with a clear description for 'sessionId'. The tool description adds only the qualifier 'high-level', which is already present in the main description. It does not provide additional meaning or usage hints beyond what the schema offers. Baseline 3 is appropriate given full schema coverage.

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 states a specific verb ('Fetch') and resource ('high-level SDK session status') and clearly indicates the identifying input (session ID). It somewhat distinguishes from siblings like 'sap_fetch_session' which likely fetch the full session object, not just status. However, 'high-level' is vague and 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?

No guidance on when to use this tool versus siblings like 'sap_fetch_session' or 'sap_session_read_latest'. No context about prerequisites, alternatives, or when not to use it. The description is purely functional without usage direction.

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