nex_browser_get_text

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

With readOnlyHint already provided by annotations, the description adds key behavioral context by specifying 'visible text' (excluding hidden text) and the scoping between 'page' and 'target'. This goes beyond annotation-level safety info.

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?

A single, focused sentence with no filler. Every word earns its place and the core purpose is front-loaded.

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 read tool with 3 optional params and no output schema, the description is sufficiently complete. It defines the action, scope, and optionality, though it does not detail return format or edge cases.

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 100%, so baseline is 3. The description adds meaning by explaining that reading can be from the whole page or a specific target, clarifying the optional semantics of the target parameter beyond 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?

The description clearly states the verb 'Read' and the resource 'visible text from the page or one target', which distinguishes it from siblings like page_title or snapshot. It is specific and concise.

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 implies usage (reading visible text when needed) but does not explicitly contrast with alternatives like snapshot or page_title, nor provide exclusions or when-not-to-use guidance.

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