page_expectRoute

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

Discloses all key behaviors: no polling, no error thrown, return format, path formatting requirement (no leading slash, no query). Without annotations, this fully informs agent of tool's behavior.

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?

Three concise sentences covering purpose, return value, and usage caveats. No wasted words, front-loaded.

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 two parameters and no output schema, the description fully covers what, how, return format, preconditions, and alternatives. Complete for agent to select and invoke 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?

Adds meaning for 'path' parameter beyond schema by specifying formatting constraints. The 'connection' parameter already has schema description, so description adds less value there overall.

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 it's a one-time assertion for page path equality, with explicit behavior (no polling, no error thrown, returns pass:false on failure). It distinguishes from sibling tools like page_waitRoute.

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?

Provides direct when-to-use guidance: if route may be unstable, use page_waitRoute first. Also implies single check, not polling.

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