chatbuy_login

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

Without annotations, the description discloses key behaviors: it opens a real browser, requires human interaction for login, and stores the session locally. It also notes the session persists, which is important for understanding state. However, it does not explain what happens if the session expires.

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 two concise sentences, in both Japanese and English, making the purpose clear without unnecessary detail. Each sentence contributes to understanding the tool's behavior.

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?

While the tool's basic behavior is explained, the single parameter 'site' is completely unexplained, and there is no information about return values or error conditions. For a tool with minimal schema detail, this is a significant 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 schema includes a 'site' parameter with no description and the tool description does not explain what 'site' refers to. With 0% schema coverage, the description fails to compensate, leaving the agent without guidance on what value to pass.

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 real browser to the login page, with a specific verb and resource. It distinguishes itself from siblings like chatbuy_search and chatbuy_status by focusing on the manual login step.

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 implies this is a one-time manual login setup that persists locally, but it does not explicitly state when to use it relative to other tools or any exclusions. The guidance is implied rather than explicit.

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