artex_login

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

With no annotations, the description adds meaningful behavior by noting that credentials come from server-side configuration and the JWT stays inside the MCP process. However, it omits token lifetime, overwrite behavior, and failure outcomes, leaving gaps for an authentication operation.

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 sentence conveys the core action and two key behavioral points with no wasted wording. The credential source and token handling are front-loaded and easy to scan.

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 zero-parameter login tool without annotations or an output schema, the description explains where secrets come from and how the JWT is stored. It still leaves the agent without explicit invocation context, success signaling, or token-expiry details, so it is adequate but 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 zero parameters, so there is no parameter semantics burden beyond the schema. The description correctly avoids restating an empty input schema and focuses on the authentication behavior instead.

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, 'Sign in', and clarifies the authentication resource, making the tool's action clear. It distinguishes itself from mutation siblings like artex_change_password and artex_logout, but does not explicitly contrast with artex_initialize or artex_configure_basic_auth.

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 implies this tool is used for authentication, but it does not explicitly state when to call it versus alternatives or whether it should be invoked before other tools. Usage is inferable from the login context rather than spelled out.

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