login

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

The annotation openWorldHint=true already indicates external side effects, and the description adds useful behavioral context: auto-generates TOTP and stores session internally. It does not contradict the annotation, but does not disclose failure handling or credential requirements, which would be helpful.

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 three short sentences, each providing distinct information: the action, the TOTP auto-generation, and the session storage. It is perfectly sized, front-loaded with the main purpose, and contains no redundant wording.

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?

Given the tool's simplicity (no parameters, no output schema), the description covers the core behavior. It could be more complete by explicitly stating that this must be called before other tools, but the session storage mention implies this, and the annotation covers external effects.

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?

With zero parameters, the description's note about auto-generating TOTP explains why no TOTP parameter is needed, adding semantic value beyond the empty schema. This fits the baseline of 4 for zero-parameter tools and slightly enhances it.

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 authenticates with Angel One SmartAPI, using a specific verb and resource. It also adds distinguishing details about TOTP generation and internal session storage, separating it from related tools like logout or get_profile.

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 that authentication is a prerequisite for other API calls by noting it stores the session internally, but it does not explicitly state when to use it or mention alternatives like logout. The usage context is inferable but not clearly articulated.

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