Check Albert Heijn Login Status

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

The readOnlyHint annotation already establishes this is a safe read operation. The description adds useful context by listing what is returned (member identity, Bonus card details, connection status), which matters because there is no output schema, but it says nothing about behavior when unauthenticated, latency, or how a failing session is reported.

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 efficient sentences with the core purpose front-loaded and the return contents following. Minor redundancy in pairing 'Check authentication status' with 'verify session', but nothing wasteful.

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 zero-parameter, read-only tool, the description is largely sufficient: it explains the purpose and the return contents in lieu of an output schema. It omits the unauthenticated/failure path, which would be the main remaining thing an agent needs.

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 tool takes zero parameters, so per the baseline for 0-param tools this scores 4. The description cannot add parameter meaning, and none is needed.

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 clear verb and resource ('Check authentication status or verify session with Albert Heijn'), so an agent knows this is an auth/session check rather than a data fetch. However, it does not explicitly differentiate itself from the similarly named sibling ah_get_profile, which also surfaces member identity.

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?

Usage is only implied: 'check authentication status' suggests calling it before other authenticated operations, but the description never states when to use it versus alternatives like ah_get_profile, nor any prerequisites. No explicit when/when-not guidance is provided.

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