Authenticate the Local API

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

The description discloses that the tool modifies the running desktop app state by storing a JWT and validating it, going beyond annotations which only indicate a mutation. It also reveals the fallback-to-server-token behavior, providing useful context without contradicting annotations.

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 two short sentences that front-load the core action ('Store... and validate it') and add only the essential default behavior. Every word contributes, with no repetition or filler.

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 tool with a single parameter, no output schema, and straightforward behavior, the description covers the purpose, the side effect, and the parameter default. It could mention that this authentication is a prerequisite for some local operations, but the title and context make that reasonably clear.

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 input schema already documents the token parameter with its fallback behavior ('Falls back to the server's DOLPHIN_API_TOKEN'). The description reiterates this fallback but adds no new semantic detail, so it stays at the baseline for high schema coverage.

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 uses a specific verb ('store' and 'validate') and names the exact resource ('remote JWT inside the running Dolphin{anty} desktop app'). It clearly distinguishes this tool from all sibling tools, none of which perform authentication.

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 conveys clear usage context by stating the default behavior ('Defaults to the token this server is configured with') and implies the tool is for authenticating the local API. It does not explicitly list exclusions or alternatives, but no sibling tool competes for this role.

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