Estado de sesión DUTIC

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

With no annotations, the description carries the burden of behavioral disclosure. It describes the tool as read-only and specifies the outputs: session validity, semester, and expiration date. While it does not mention side effects or rate limits, for a simple status check this is adequate and does not contradict any annotations (none provided).

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, efficient sentence with no redundant information. Every word adds value, making it concise and easy to parse.

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?

Given the tool has no parameters and no output schema, the description fully covers its functionality and expected output. It tells the agent exactly what information the tool returns (session validity, semester, expiration), making it complete for this simple tool.

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?

The tool has zero parameters, so the description needs no parameter explanation. Baseline score of 4 applies as per guidelines, as the description adds no parameter semantics beyond what is inherent to a no-parameter tool.

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 that the tool indicates session validity, the current semester, and expiration date. It uses a specific verb ('Indica') and identifies distinct resources (session, semester, expiration), distinguishing it from sibling tools that deal with grades, courses, or other data.

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 the tool is used to check session status, likely before performing other operations, but it does not explicitly state when to use it or when not to. No alternatives are provided, but the purpose is clear enough for an agent to infer its role as a prerequisite check.

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