Login to Medium

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

No annotations are provided, so the description carries the full burden. It discloses that the tool opens a browser window and that session persistence requires a separate save_login call, which is useful. However, it does not explain what happens on successful login, how failures are handled, whether it checks for an existing session, or what the return value is. Given the lack of annotations, more behavioral detail is expected.

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 exactly two sentences: the first states the core action, the second provides a follow-up action in context. There is zero fluff, and the information is front-loaded. Every sentence earns its place.

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 tool with no parameters, no output schema, and no annotations, the description covers the essential context: what it does, when to call it, and what to do next. It omits edge cases (e.g., already logged in, login failure), but given the simplicity of the tool, the description is nearly complete. Sibling tools like login_status may cover additional context.

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 schema defines zero parameters, so schema coverage is trivially 100%. The baseline for 0 parameters is 4, and the description correctly avoids adding unnecessary parameter details. There is nothing to explain about parameters, so a 4 is appropriate.

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 opens a browser window to log in to Medium, using a specific verb+resource construction. It distinguishes from sibling tools like save_login and logout by explicitly positioning login as the initial authentication step, and it mentions save_login as a follow-up, which helps disambiguate.

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 provides clear workflow guidance: 'After logging in, use save_login...' indicates when to use login versus save_login. It also implies that login is a prerequisite for member-only content. It lacks explicit exclusions (e.g., 'do not use if already logged in'), but the mention of save_login and the login context gives sufficient direction.

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