s21_open_interactive_portal

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only says the tool 'opens' the portal and lists UI contents; it does not mention that it starts a local HTTP server, opens an application window, or has any other notable side effects. The behavioral profile is under-specified.

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, front-loaded sentence with no wasted words. The parenthetical list of UI elements adds concrete value without bloating the text.

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 simple open-tool with two optional parameters and no output schema, the description combined with the schema covers the core essentials. However, the lack of explicit usage guidance and the missing behavioral note about local server/window side effects leave minor but meaningful 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?

Schema description coverage is 100%, so the port and auto_open parameters are already well-documented in the input schema. The tool description adds no additional parameter semantics, matching the baseline of 3 for high schema coverage.

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 uses a specific verb ('Abre') and a clearly defined resource ('portal interactivo unificado'), and elaborates on the portal's contents ('bienvenida al alumno, métricas, accesos directos y catálogo de herramientas'). This distinguishes it from sibling tools like s21_open_exam_simulator, making the purpose unmistakable.

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 when to use the tool: when the user wants the unified interactive portal dashboard. However, it does not explicitly state when not to use it or which sibling alternatives might be better suited for specific tasks, leaving it to the agent to infer the boundary between this portal and the more specialized tools.

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