carrefour_clear_session

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

With no annotations, the description carries the full burden of disclosing behavior. It states 'delete' which implies a destructive action, but does not detail side effects such as whether the server session is invalidated, if authentication is required, or if this is reversible. The description is transparent about the primary action but lacks contextual behavioral details.

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, concise and front-loaded. It conveys the essential purpose without any fluff, making it highly efficient for an agent to parse.

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 tool with no parameters and no output schema, the description is largely complete. It explains exactly what action is performed. However, it could benefit from mentioning that clearing cookies may log out the user or affect the session state, but given the simplicity, it is nearly adequate. A slightly richer context would elevate completeness, but it is not critically incomplete.

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 has no parameters, and the schema is empty with 100% coverage. The description does not need to explain any parameters, and the baseline for zero parameters is 4. The description adds no irrelevant parameter info, so it 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 action ('Delete') and the resource ('locally stored Carrefour cookies'). It easily distinguishes from siblings like carrefour_set_cookies (sets cookies) and carrefour_refresh_session (refreshes session), as it specifically describes deleting local cookies.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that this is likely for logging out or clearing a session, nor does it exclude any usage scenarios. Without context, an agent may not know when to select this over carrefour_set_cookies or carrefour_refresh_session.

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