login

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

With no annotations provided, the description carries the full burden of disclosure. It discloses key behavioral traits: token verification via tokeninfo and storage in the server session, and the effect on subsequent calls. It does not mention failure modes or session expiration, but the core side effects are transparent enough 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?

The description is a single, tightly written sentence with a dash to separate the main action from its consequence. Every phrase adds value: what it does, how it does it, and the follow-up effect. No wasted words.

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?

The tool is simple (one parameter) and has an output schema, so the description does not need to explain return values. It thoroughly explains the process and the resulting session state, which is sufficient for the agent to use the tool correctly in a typical flow.

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 coverage is 100% and the parameter description 'issued business token' is clear. The tool description adds a bit of context by saying 'Login with business token,' but it does not provide additional semantic meaning beyond the schema. The baseline of 3 applies since the schema already documents the parameter well.

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 action: 'Login with business token' and the resource (business token). It specifies the process: verify through tokeninfo and store in server session. This distinguishes it from siblings like logout and use_account, which have different purposes.

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 gives clear context that after login, subsequent tools are called without a token argument, implying login should be done before other calls. It does not explicitly mention when not to use it or alternatives, but the sequencing guidance is strong enough for the agent to decide when to invoke.

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