read_page

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

No annotations are provided, so the description carries the full burden and mostly succeeds: it discloses the environment (real Chrome via OctoLimb extension), the default omission of body text, and that indices must be refreshed before acting. It does not cover failure modes such as stale indices or empty/detached tabs, which leaves a small gap for a browser-driving tool.

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 bracketed context note is front-loaded, followed by what is returned, when to call it, and the include_text caveat. Every sentence adds actionable information with no filler.

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?

With no output schema and no annotations, the description must explain return shape and it does (URL, title, indexed elements) as well as the default text behavior. An agent has everything needed to call it correctly and interpret the result.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds intent beyond the schema: include_text should be passed only when page content is genuinely needed, not for interaction. It also reinforces that omitted text is the default, though max_text_length and viewport_expansion are left entirely to the 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?

States a specific verb and resource ('Read the current page in this task's tab') and enumerates exactly what comes back: URL, title, and an indexed list of interactive elements. This cleanly separates it from siblings like click_element or input_text, which act rather than read.

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 both when-to-use ('use only when the task requires acting on a real website') and an explicit ordering rule: call this before click_element, input_text, or the dropdown tools to get valid indices. It also names the condition for the text-reading variant versus mere interaction.

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