login

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

With no annotations, the description carries the full behavioral disclosure burden. It discloses the OAuth2 method, the browser interaction, and the resulting profiling capability. However, it does not explicitly state that the process requires a human to complete login, that it may block while waiting, or what happens to existing authentication state.

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 clear, front-loaded sentences with no filler. Each sentence adds essential information: the authentication method, the browser side effect, and the resulting benefit.

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 login tool with one parameter and no output schema, the description covers the key aspects: purpose, authentication mechanism, browser interaction, and what the authentication enables. It could be more explicit about the interactive nature and post-login behavior, but it is largely 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?

The schema provides 100% coverage of the single parameter, storeUrl, including a description and example. The tool description does not add extra semantic detail about the parameter, which is acceptable given full schema coverage, so the baseline score of 3 applies.

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 specific action ('Authenticate with Shopify via OAuth2'), the resource (Shopify), and the method (browser-based OAuth2, same as Chrome Theme Inspector). It also distinguishes itself from sibling tools by mentioning the browser flow and the full flame graph profiling data it enables.

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 provides clear context: use this tool to authenticate via OAuth2 in a browser and to get access to flame graph profiling data. It doesn't explicitly mention when to avoid this tool or list alternatives, but the browser-based OAuth2 method and the purpose are enough to guide typical usage.

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