ddb_get_page

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

Beyond the readOnlyHint annotation, the description adds that the browser stays open and directs the caller to ddb_close_browser. This is important persistent state information. It also clarifies that the tool returns text, not HTML or other content. However, it doesn't describe output format or error cases, but annotations cover the safety aspect.

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 sentences, front-loaded with the primary action, and the second sentence adds a critical behavioral note without waste. Highly concise.

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 zero-parameter, no-output-schema tool, the description covers the action and the post-requisite (close browser). It could describe the return format more explicitly, but 'text content' is sufficient for this context.

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 has zero parameters, so the baseline is 4. The description explains the implicit input is the 'currently loaded page,' clarifying that no explicit arguments are needed. This adds meaning beyond the empty schema.

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: 'Return the text content of the currently loaded page in the browser.' This specifies a verb, resource, and scope, and distinguishes it from sibling tools like ddb_close_browser (closing) and ddb_navigate (navigating).

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 clear context: use this to retrieve the current page's text. It also instructs to call ddb_close_browser when finished, implying a usage flow. However, it doesn't explicitly discuss when not to use it or compare to alternatives.

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