delhaize_auth_status

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

With no annotations, the description carries the full burden. It discloses the return structure (logged_in, message), the consequence of being logged out (user must run a separate command), and a critical constraint: the server cannot and must not perform the login itself. This is valuable behavioral context beyond a simple status check.

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?

Three sentences, each front-loaded with the key information. No redundancy; every sentence adds a distinct piece of information: purpose, return shape, and prerequisite action.

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 no annotations, no output schema, and zero parameters, the description is complete enough for an agent to use correctly. It explains what the tool does, what it returns, and what to do if the session is invalid. No critical gaps for a simple status-check tool.

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?

There are zero parameters, so the baseline is 4. The description correctly implies no inputs are needed, and it documents the response shape, which compensates for the lack of an output schema.

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?

States a specific verb and resource: check whether the saved Delhaize browser profile is still logged in. An agent can distinguish this from siblings like list_receipts or fetch_promotions, which are about data retrieval, not session validity.

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?

Implies the tool should be used before operations that require an authenticated session, and the description explicitly states a prerequisite: if logged_in is false, the user must run 'delhaize-receipts login'. It doesn't explicitly name which siblings require this check, but the context is clear.

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