Log in to PushEngage

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

The description discloses critical behavioral traits: interactive browser opening, storing the token locally, showing expiry, and printing a manual URL in headless environments. This goes well beyond the sparse annotations (readOnlyHint=false, openWorldHint=true, etc.) to give the agent a complete picture.

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 three concise sentences, front-loaded with the primary action ('Opens a browser window...'). Every sentence adds valuable context without verbosity.

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 fully covers the tool's operational context: environment requirements, interactive flow, token storage, result contents (expiry), and manual fallback. It is sufficient for an agent to decide when and how to invoke it.

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 takes zero parameters, so the schema is fully covered and there is nothing for the description to explain. The baseline score of 4 applies here.

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 function: it opens a browser window to the PushEngage dashboard for authorization. This distinguishes it from the sibling auth tools (status, logout) by describing the unique OAuth login flow.

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 mentions the browser requirement and the fallback for headless/SSH environments, giving clear context for when manual intervention is needed. It doesn't explicitly contrast with auth_status or auth_logout, but the usage context is implied sufficiently.

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