Close Debeka Browser

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

The description adds useful behavioral context beyond the annotations: it closes the browser instance, frees resources, and returns a confirmation. The annotations already indicate idempotence and non-destructiveness, so the description's resource-freeing note and return-value statement are meaningful supplements without contradicting the 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 short and front-loaded, with the primary action stated in the first sentence. Every sentence earns its place: the trigger context, the resource-freeing rationale, and the return value are all concise and relevant.

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 zero-parameter tool with no output schema, the description is complete: it states what happens, why to call it, when to call it, and what to expect in return. No additional context is needed for an agent to select and invoke this tool correctly.

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 tool has no parameters, and the schema has complete coverage. The description does not need to explain parameter semantics, and it adds value by clearly stating the tool's side effect and return value instead.

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 uses the specific verb 'Closes' with a clear resource ('the browser instance'), and the context 'when you're done with the Debeka form' makes the tool's role unambiguous. It is clearly distinct from sibling tools like debeka_open_page or debeka_submit, which perform different actions on the form.

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 explicitly states when to call this tool: when done with the Debeka form to free up resources. It does not mention when not to call it or list alternatives, but the 'done with the form' trigger is sufficient for a simple close operation, and no sibling tool serves the same purpose.

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