usp_login

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

The description discloses that the password is encrypted before transmission and never stored, which is helpful. However, it does not mention session management, authentication state, or side effects like cookie creation. With no annotations, the burden is higher, but some transparency is 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?

Three sentences that are front-loaded with the action, followed by a security note and return value. No fluff, every sentence adds value.

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 presence of an output schema, the description's mention of returning a profile is sufficient but lacks details on error handling, session tokens, or the broader authentication flow. It is adequate but not comprehensive.

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 the description must compensate. It mentions 'USP number and Senha Única' but does not explicitly map to parameter names (usp_username, password) or provide format constraints. Minimal additional meaning beyond the 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 action: logging in to USP using a USP number and password (Senha Única). It distinguishes from sibling tools like usp_logout and others focused on schedules, grades, etc.

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?

Usage is implied as a prerequisite for other tools requiring authentication, but there is no explicit guidance on when to use it versus alternatives, or any mention of prerequisites.

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