login

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

With no annotations, the description bears full burden. It discloses environment variable usage, defaults, and multi-school subdomain support, but does not mention side effects (e.g., session handling, authentication mechanism) or failure behavior beyond 'error message'.

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 well-structured with an overview, args list, and returns. It is not overly verbose, though some repetition (e.g., environment variables mentioned twice) could be trimmed. The first sentence is front-loaded and clear.

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?

The description covers core functionality and return value, but is incomplete on prerequisites (e.g., internet connection, valid Edupage account) and error handling details. Output schema exists but is not shown; description's return statement is minimal. Given low complexity, it's acceptable but could be more thorough.

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 coverage is 0%, so description compensates. It explains each parameter's purpose, default from env vars, and that subdomain accepts comma-separated list for multiple schools. While it lacks format constraints, it adds significant meaning beyond the bare schema.

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 the tool's purpose: 'Log in to Edupage using environment variables.' It specifies the resource (Edupage) and the action (login), and distinguishes from sibling 'login_auto' by emphasizing environment variable usage and multi-school support.

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 explains when parameters are optional (if env vars set), defaults, and multi-school support. However, it does not explicitly contrast with the sibling 'login_auto' tool, missing an opportunity to clarify when to use each. No 'when not to use' guidance is provided.

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