epf_login

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

With no annotations, the description carries the full burden. It discloses that authentication produces a JWT and that store=true makes that JWT the active session credential, which are important behavioral side effects. It does not describe failure behavior, but for a simple auth call the key state-changing effect is covered.

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?

Two short sentences, front-loaded with the core action and followed by the optional parameter behavior. Every word adds value and there is no redundancy.

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 three-parameter authentication tool with no output schema, the description covers the main action and the key session-storing side effect. It lacks guidance on error cases and does not position login relative to epf_reauth, which leaves some contextual gap for an agent.

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 0%, so the description must compensate. It maps login and pword to username/password and, more importantly, explains the store parameter's meaning beyond its boolean name: it controls whether the resulting JWT becomes the active session credential.

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 ('Authenticate') and names the resource ('EPF'), making the operation unmistakable. It clearly distinguishes this tool from siblings like epf_logout, epf_version, and epf_download_list.

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 states the tool is for authentication and explains the optional store parameter. However, it does not explicitly contrast login with epf_reauth or state when one should be used over the other, so usage guidance is only implied.

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