veil_forward

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

Discloses error behavior for empty history and waitUntil defaults ('load' or 'networkidle'), providing useful context. No annotations exist, so description carries full burden; it partially covers the behavioral profile, but could mention return values or side effects.

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?

Extremely concise: one sentence with critical info front-loaded. Every word serves a purpose—action, condition, parameters—with no redundancy.

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 core behavior (forward navigation, error, waitUntil) adequately for a simple action tool with no output schema. Minor gaps: no mention of return values or interaction with frames, but sufficient for basic use.

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?

Adds value beyond the enum-only schema by stating default ('load') and the purpose of the parameter (waiting condition). For a single parameter with 0% schema description coverage, this elevates understanding significantly.

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 action: 'Go forward one entry in session history' with a specific verb and resource, and expertly distinguishes from sibling tools like veil_back. The error condition 'errors if there's nothing later' adds precision.

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?

Mentions the waitUntil parameter options and default, and implies when-to-use by warning about empty history. However, lacks explicit guidance on when not to use this tool (e.g., preferring veil_goto for direct navigation) and no comparison to alternatives.

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