Sign in to Picnic

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

Goes well beyond the annotations: one-time 127.0.0.1 address, 5-minute expiry, the exact credentials requested, SMS/e-mail code step, token written to the system credential store, and an explicit security assurance that the password never reaches Claude. This is exactly the extra context a non-destructive but non-idempotent, open-world tool needs.

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?

Front-loads the action ('Open a sign-in page...'), then layers mechanism, security, and usage trigger in descending priority. Dense but every clause carries information an agent cannot get from the schema or annotations.

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?

Adequate for a zero-param tool with no output schema: the agent knows what will happen and why. A small gap is that it does not say what to do after signing in (e.g., retry the tool that reported the missing session), though that is reasonably inferable.

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?

Zero parameters, so the baseline is 4. The description correctly implies no input is required and instead describes the interactive flow the user will go through, which is the useful substitute for a parameter list 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?

States a specific verb and resource ('Open a sign-in page for Picnic'), plus the execution locus (user's browser) which separates it from any hypothetical server-side auth. No sibling tool shares this purpose, and the auth scope is unmistakable.

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?

Gives an explicit trigger condition: 'Use it when another tool reports that no session is stored.' That is a concrete, checkable precondition rather than an implied one, and it correctly frames this as the fallback for the session-dependent siblings.

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