status

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

With no annotations, the description carries the full burden. It does disclose what the response contains (connection state, consentId, intercepted headers), which implies a read-only inspection with no side effects, but it never states that explicitly and gives no indication of what happens when no session exists or what the header data means.

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?

A single short sentence with no padding, and the resource is front-loaded. It is slightly undermined by mojibake encoding ('État', 'interceptés') and by the cryptic closing phrase, which costs a little readability.

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?

With no annotations and no output schema, the description is the only source of information about what comes back, and it gives just a three-item summary. 'Headers API interceptés' is unexplained, so an agent cannot anticipate the shape or reliability of the returned data.

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 there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The description's mention of returned fields is a small bonus rather than a parameter explanation.

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 says the tool returns session state ('État de la session') and names concrete fields: connection status, consentId, and intercepted API headers. That is more informative than the bare name 'status', but there is no verb and the purpose is expressed as a data listing rather than an action, leaving the intent only implied.

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?

There is no statement of when to call this, no prerequisites, and no reference to alternatives. The sibling tools are all cart operations and none are related, so no routing guidance was strictly possible, but the description offers no usage context at all.

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