verify_action

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

Discloses navigation behavior, verification logic per action type, and optional URL. Lacks details on error handling or timeout, but overall transparent for a verification tool. No annotations provided, so description carries burden.

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?

Description is well-organized with a general statement followed by arg details. A bit lengthy but no superfluous text. Every sentence adds value.

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?

Covers usage, params, and behavior adequately. Output schema exists but not shown; description doesn't need to repeat return format. Could mention verification failure outcomes, but not essential.

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?

With 0% schema coverage, description adds vital context: action_type values (delete/edit/toggle), target_text semantics per action_type, and verify_url fallback. Enables agent to use params correctly.

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?

Description clearly states it verifies that a destructive action persisted by navigating and checking page content. It distinguishes itself from siblings (e.g., test_action) as a post-action verification tool.

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?

Explicitly says 'Call this AFTER performing a delete, edit, or toggle and seeing a success message.' Provides clear when-to-use guidance without mentioning alternatives but context is sufficient.

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