auth

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

No annotations are present, so the description carries the full burden of disclosing side effects such as session creation, invalidation, or read-only status. 'Manage PRO authentication' reveals nothing about whether actions mutate state, require prior login, or what responses look like.

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 only four words, which is terse but not effectively concise—it omits nearly all relevant information. Under-specification is not the same as conciseness; every word should earn its place, and here the words communicate only a vague domain.

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 output schema, no annotations, and a single action enum, the description must explain the tool's behavior, side effects, and expected return states. It does none of that. The description is insufficient for an agent to confidently invoke the tool with correct expectations.

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?

Schema description coverage is 0%, and the description adds no meaning to the single 'action' parameter. It does not explain the semantics of login, logout, or status, nor how each action behaves. The enum names are self-explanatory but the description itself contributes zero parameter 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?

The description says 'Manage PRO authentication,' which names a resource but uses the generic verb 'manage' and does not specify the concrete actions (login/logout/status) beyond what the schema provides. It is not clearly differentiated from sibling tools like status or detect_login_form.

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?

There is no guidance about when to use this tool versus any alternatives. The description does not mention login forms, session management, or any exclusion criteria, leaving the agent to infer usage only from the action enum.

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