get_ws_token_legacy

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

Discloses key behavioral traits: token is short-lived (60s), single-use, and requires API credentials. No annotations exist, so the description covers the safety and usage constraints well, though it could mention any side effects (none expected).

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?

Two concise sentences with no fluff. Every sentence adds value: first defines what it does, second gives usage guidance. Front-loaded with critical info.

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 zero-parameter tool with no output schema, the description fully covers purpose, usage context, constraints (duration, single-use), and requirements (credentials). No gaps.

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?

No parameters in schema, and description adds no parameter details—unnecessary. Baseline 4 is appropriate as schema coverage is 100% and description does not need to compensate.

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?

Clearly states it mints a short-lived token for the legacy /stream endpoint, specifying the verb 'mint', the resource 'token', and the context 'legacy public /stream endpoint', which distinguishes it from sibling get_ws_token.

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?

Explicitly instructs to prefer get_ws_token for new code and explains this tool is for /stream compatibility, providing clear when-to-use and when-not-to-use guidance.

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