learnus_auth_status

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

The annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds genuinely non-obvious behavioral context beyond them: data tools authenticate automatically, and a false status does not imply that manual login is needed. That is exactly the kind of semantic guidance structured fields cannot carry.

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?

Three sentences, front-loaded with the purpose and then the usage constraints. Every sentence earns its place, and the counter-intuitive warning is placed last but clearly scoped.

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 status probe with no output schema, the description covers what the tool does, when to invoke it, when not to, and how to interpret a negative result. No important invocation context is missing.

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 to document and the baseline is a 4. The description correctly avoids inventing parameter behavior, though it also does not describe what the returned status values look like.

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?

States a precise verb and resource: reports whether the current MCP process has an authenticated LearnUs session. It also distinguishes itself from the sibling data tools by clarifying that it is a status check, not a data accessor.

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 scopes usage to the case where the user directly asks about login/session state, and explicitly forbids using it as a prerequisite for data calls. It also preempts a likely misinterpretation (that a false status requires manual browser login).

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