zerodom_read_page

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly states the key behavioral trait: this tool 'does not reload, so anything typed into the page stays.' It does not describe the return format, but an output schema exists and the most important side-effect distinction is disclosed. No contradiction with annotations.

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 two sentences with no filler. The core purpose is front-loaded, followed by a precise when-to-use statement and a clarifying contrast with the sibling tool. Every sentence earns its place.

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 low-complexity tool with a single optional boolean and an output schema present, the description supplies the essential usage context, the stale-node-id trigger, and the critical non-reload caveat. The undocumented 'verbose' flag is a minor gap but does not prevent correct invocation since it is optional and has a sensible default.

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 only parameter, 'verbose', is never mentioned in the description and schema description coverage is 0%. The schema provides only the type and default, leaving the agent to infer what verbose output means. The description adds no parameter-level meaning.

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 immediately states a specific action and resource: 'Re-read the current page without navigating.' It also distinguishes itself from zerodom_parse_url by the reload behavior, making clear it is not a navigation-triggering action and separating it from the listed sibling tools.

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 gives explicit conditions for use: 'after an action changed the page, or when node ids look stale.' It also names the alternative, zerodom_parse_url, and explains why that alternative is not chosen: it reloads and would lose typed content.

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