Log in to Money Forward ME with a browser

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

Discloses side effects: opens a browser (consistent with openWorldHint) and stores cookies (consistent with non-read-only annotation). Does not note any destructive actions, which is acceptable for a login tool.

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?

Two sentences, no fluff: first explains action, second gives alternative usage. Front-loaded with core purpose.

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?

Sufficient for a single-parameter tool with an output schema (not shown but indicated). Describes the login flow and cookie storage. Could mention credentials handling, but not critical.

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 covers the only parameter (headless) with 100% description coverage. The tool description adds no extra parameter semantics beyond what the schema already provides.

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 it opens a Playwright browser login flow and stores cookies locally. It distinguishes from sibling tools like set_cookie by mentioning remote server context.

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 tells when to use set_cookie instead (for remote servers). Also implies headed mode for MFA via the headless parameter description. Could provide more guidance on when to use auth_check vs login, but overall clear.

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