auth_get_status

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

No annotations are provided, so the description carries the full behavioral burden. The 'GET' verb hints at a read-only call, but the description never states whether authentication is required, what the status payload distinguishes (e.g., authenticated vs. anonymous vs. expired), or what happens on failure.

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?

Extremely short and front-loaded, which is good, but roughly a third of the text is an HTTP route echo and a 'Tags:' artifact that add no decision-relevant information for an agent. It is terse rather than economical.

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, no output schema, and no parameter schema, the description is the only source of truth, and it omits what the status value means and any auth prerequisite. For an auth-status endpoint that an agent may use to decide whether to log in, this is a real gap.

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 the schema carries no semantics to document and the baseline is 4. Nothing in the description conflicts with the empty schema.

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 verb and resource ('Get the status of the authentication'), which is understandable, but it essentially restates the tool name and adds no differentiation from siblings such as auth_login, auth_register, or auth_passkey_authentication_verify. An agent cannot tell what 'authentication status' actually reports.

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?

No guidance on when this endpoint should be called versus the other auth_* tools, nor any prerequisite (e.g., whether a session/token is required first). The Tag fragment 'Auth Controller' is generator metadata, not usage guidance.

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