browser_type

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

No annotations provided, so the description carries full burden. It mentions execution timing but does not describe the primary behavior (e.g., whether it clears the field first, what happens on success/failure, or what the tool returns). The output schema exists but is not referenced.

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 poorly structured: it starts with a clunky header, then dives into execution timing advice without first stating the tool's purpose. It is not front-loaded and contains unnecessary filler ('Kali Agent MCP tool:').

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 the tool has 9 parameters and an output schema, the description is completely inadequate. It does not explain the primary function, most parameters, or the output. The agent cannot reliably invoke this tool based on the description alone.

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 0%, so the description should explain each parameter. It only discusses timing parameters (expected_runtime_seconds, timeout_seconds, etc.) but does not explain core parameters like selector, text, session_id, or clear. The description adds minimal value 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 fails to state that this tool types text into a browser element. It starts with 'Kali Agent MCP tool: browser_type Explicit execution timing is supported' which does not clarify the core action. The purpose is only inferable from the tool name 'browser_type' and parameters (selector, text).

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 sibling tools like browser_click, browser_text, or browser_navigate. The description only gives internal advice on setting timeout parameters, not the context or alternatives.

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