登录医联预约平台

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

The description discloses that the session is encrypted and saved locally, which is beyond the non-existent annotations. However, it doesn't explain other behavioral aspects like returning a token, setting cookies, or error conditions.

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 a single concise sentence that front-loads the primary action. It is efficient but could be improved by listing parameters or adding structure.

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 login tool with no output schema and no annotations, the description is insufficient. It doesn't explain return values, error handling, or the flow involving SMS code. Sibling tools suggest a multi-step auth process, but this tool's role is not fully contextualized.

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?

Description mentions username, password, and SMS code, covering 3 of 4 parameters. It adds meaning to these parameters. However, flowId is not described, and with 0% schema coverage, the description should cover all parameters.

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 clearly states the tool logs in using login name, password, and SMS code, and mentions encrypting the session. The title reinforces the platform context. However, it doesn't explicitly differentiate from sibling auth tools like auth_get_captcha or auth_send_sms_code.

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 to use this tool versus alternatives. It doesn't mention prerequisites (e.g., requiring an SMS code) or that it should be used after auth_send_sms_code. The description only implies use for logging in.

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