login

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

With no annotations, the description carries the burden and does disclose a genuinely non-obvious behavior: the conditional return of 'pin_required' and the handoff to submit_pin. It omits auth/permission requirements, credential handling, and failure behavior, so it is strong but not exhaustive.

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?

Three tight sentences with the core purpose front-loaded, followed by the prerequisite and the pin-flow contingency. No filler; each sentence adds an actionable fact.

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?

An output schema exists, so return-value detail is not strictly required, yet the description still flags the important 'pin_required' branch. Purpose, prerequisite, and follow-up are covered; the undocumented 'lang' parameter is the main remaining 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?

Schema description coverage is 0%, so the description should compensate. It adds real meaning for 'login' ('login starts with 4'), but says nothing about 'password' or the 'lang' parameter, leaving two of three parameters undocumented in both schema and description.

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?

States a specific verb (Create) and resource (personal webQUIK session) scoped to this MCP connection. It is easily distinguished from siblings like logout and session_status, and the phrase 'personal... for this MCP connection' signals per-connection session semantics.

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?

'Required before any trading or market-data tools' gives an explicit prerequisite and effectively tells the agent when this tool must be called versus skipped. It also names the follow-up alternative ('then call submit_pin'), routing the agent through the SMS flow.

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