neko_get_state

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

With no annotations, the description carries the behavioral disclosure burden. It accurately states the output includes URL, title, interactive elements, and optionally a screenshot, implying a read operation. However, it does not disclose potential side effects (e.g., whether the state is cached or forces a re-render) or clarify if the interactive elements are obtained via accessibility tree or DOM traversal.

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?

Single sentence of 18 words with no fluff. The core action ('Get the current browser state') is front-loaded, and the optional screenshot is mentioned last. Every word serves a purpose.

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?

Given no output schema, the description adequately lists the return components: URL, title, interactive elements, and optional screenshot. It does not specify the format of interactive elements (e.g., selector, text, role), but for an agent this is sufficient to understand the tool's purpose. Slightly more detail could improve completeness.

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% with descriptions for both max_elements and include_screenshot. The description does not add new parameter context beyond what the schema already provides. Baseline score of 3 is appropriate.

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 retrieves the current browser state including URL, title, interactive elements, and optionally a screenshot. This distinguishes it from siblings like neko_screenshot (only screenshot) and neko_get_html (only HTML). The verb 'Get' and listed components provide specificity.

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?

No guidance on when to use this tool versus alternatives. For example, if only a screenshot is needed, neko_screenshot would be more appropriate. The description does not mention any prerequisites (e.g., page must be loaded) or exclusions.

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