passgage_login

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

With no annotations, the description carries full burden for behavioral disclosure. It states that login returns a JWT token but does not mention failure behavior, token storage, session side effects, or security considerations. This is a notable gap for an authentication tool.

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 sentence that is direct and front-loaded, conveying the essential action and purpose without wasting words. Every element earns its place.

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 authentication tool with two well-described parameters and no output schema, the description provides the core information needed for basic usage. However, it lacks guidance on error responses or next steps, which would make it fully complete.

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 100% with clear property descriptions ('User email address', 'User password'). The description simply repeats the parameter names without adding syntax or formatting details, so it does not exceed the baseline value provided by 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 verb 'Login', the resource 'Passgage API', the method (email and password), and the outcome (get JWT token). This distinguishes it from sibling tools like passgage_refresh_token and passgage_logout, which handle different auth lifecycle stages.

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 usage as the entry point for authentication but does not explicitly state when to use it versus alternatives like refresh_token or auth_status. No exclusionary guidance is provided, leaving the agent to infer the appropriate context.

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