assert_url_matches

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

With no annotations, the description carries the full burden, but it only discloses the matching modes (substring or regex). It does not say what happens when the assertion fails, whether the tool waits or retries, or how the result is reported to the agent.

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 one tightly worded sentence with no filler, and the core purpose is front-loaded. It is appropriately concise, though it sacrifices behavioral context.

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 simple two-parameter tool with no output schema or annotations, the description is not fully complete. An agent still lacks information about failure behavior and return values, which is critical for an assertion tool.

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 description coverage is 0%, so the description must explain the parameters. It adds useful meaning by clarifying that pattern can be a substring or regex depending on the regex flag, but it does not specify the default mode/substring semantics, regex syntax, or case sensitivity.

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 a specific verb ('Assert') with a clear resource ('current URL') and defines what matching means ('substring or regex'). This makes it distinguishable from retrieval tools like get_url and waiting tools like wait_for_url, though it does not name those alternatives.

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 is given about when to use this assertion versus alternatives such as wait_for_url or get_url. The verb 'Assert' implies immediate verification, but the description never states this or provides any exclusions or preconditions.

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