ddb_login

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

Discloses key behaviors: opens browser (side effect), logs in via Wizards ID, and persists session to disk. With no annotations, these details are critical and well conveyed.

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 concise sentences, front-loaded with action, no wasted words.

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?

Complete for a zero-parameter, no-output-schema tool. Covers purpose, side effect, and usage pattern. Minor gap: could mention expected return (e.g., success indicator), but not essential.

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?

No parameters exist, so high baseline. Description correctly adds no param info because none needed.

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 it opens a browser to log into D&D Beyond via Wizards ID, a specific verb-resource pair. It distinguishes from sibling tools which focus on data retrieval or status, not authentication.

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?

Explicitly says run once and session is saved for reuse, providing clear when-to-use guidance. No exclusion of alternatives, but context implies it's the initial setup step.

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