ddb_navigate

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

Beyond the readOnlyHint annotation, the description discloses critical behavioral traits: the browser persists after the call, enabling subsequent ddb_interact or ddb_get_page calls, and the need to explicitly close the browser. It also adds the domain restriction, giving the agent a clear safety and statefulness 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?

Three concise sentences, all value-dense: the first defines the action and result, the second imposes the safety constraint, and the third explains the stateful behavior and cleanup. No filler or 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 simple one-parameter navigation tool, the description covers the essential context: what it does, what it returns, its restrictions, its statefulness, and how to clean up. There is no output schema, so mentioning the text content return is sufficient.

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 input schema already provides full coverage (100%) for the single URL parameter, including the required format. The description reinforces the domain restriction but adds no new parameter-level details, so it meets the baseline without enhancing semantics.

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 with a specific verb ('Navigate') and resource ('any D&D Beyond URL'), and specifies the output ('page's text content'). It also distinguishes itself from siblings by noting follow-up ddb_interact or ddb_get_page calls, establishing its role as the navigation entry point.

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?

Provides explicit usage context: restricts to dndbeyond.com URLs, notes the browser stays open for follow-up tools, and instructs to call ddb_close_browser when finished. This effectively tells the agent when to use this tool and what to do next, though it doesn't enumerate alternatives for non-navigation tasks.

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