edenred_start_login

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

Annotations already indicate non-readonly (readOnlyHint=false) and external interaction (openWorldHint=true). The description adds key behavioral detail: 'The token stays in MCP memory and is never returned.' This clarifies token handling and emphasizes that the tool does not expose the token, which is important for security. No contradictions.

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 concise sentences that each add value. First sentence specifies the action; second provides usage trigger and token behavior. No extraneous information.

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 authentication tool with no parameters and no output schema, the description covers the essential points: action, trigger condition, and token lifecycle. It could mention return behavior (e.g., success/failure), but given that it opens an external browser, the return may be minimal. The description is adequate for an AI agent to understand when and how to use it.

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 zero parameters and schema coverage is 100%. The description does not need to elaborate on parameters. Baseline of 4 is appropriate as the description focuses on the action and usage context.

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?

Clearly states verb 'Open' and resource 'browser for local Edenred Plus login'. Specifically distinguishes from sibling tools which handle different operations (status, balances, transactions, deals) by being the authentication initiation tool. Provides explicit condition for use (AUTH_REQUIRED or AUTH_EXPIRED).

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?

Explicitly states when to call: 'Call this when Edenred tools report AUTH_REQUIRED or AUTH_EXPIRED.' This provides clear usage context. No alternative tools are suggested because the login is a prerequisite for others; thus the guidance is sufficient.

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