Refresh the INDstocks access token

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

With no annotations provided, the description carries the full transparency burden and meets it well: it discloses token lifetime, no-restart activation, server-derived TOTP behavior, transcript exposure of a passed MPIN, and revocation of any existing TOTP-issued token. This gives the agent a clear view of side effects before invocation.

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 dense but efficient: the core action and immediate effect are front-loaded, and every subsequent sentence contributes distinct operational information. There is no filler or redundant restating of the tool name.

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 two-parameter tool with no output schema and no annotations, the description covers prerequisites, authentication modes, side effects, and security considerations. The only omitted detail is exact return formatting, but that is self-evident for a refresh action and does not block correct invocation.

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?

Although the schema already describes both parameters, the description adds meaningful conditional semantics: if INDSTOCKS_TOTP_SECRET is set, no arguments are needed; otherwise a six-digit code is expected. It also connects the mpin parameter to a privacy trade-off, helping the agent decide whether to pass it or rely on the environment.

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 opens with a specific verb and resource: 'Generate a fresh INDstocks access token', and clearly states the immediate effect: 'start using it immediately'. None of the sibling tools concern token management, so the purpose is unambiguous.

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 explicitly identifies the trigger condition: 24-hour token expiry causing every other tool to fail. It also gives conditional guidance on when no arguments are needed versus when a TOTP code is required, and warns against passing an MPIN when environment credentials are available.

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