verify.assert_navigation_reached

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

With no annotations, the description carries the burden of behavioral disclosure. It makes clear this is an assertion against page source text rather than a mutation or navigation action. However, it does not disclose what happens on failure, whether it waits for the text, or whether evidence is captured, leaving meaningful behavioral gaps.

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 a single, readable sentence with no filler. It front-loads the action and resource. It is concise, though it sacrifices completeness in favor of brevity.

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?

The tool requires an existing Appium session, has four parameters, no annotations, and no output schema. The description does not explain the sourceEvidencePrefix parameter, failure semantics, or how this assertion relates to the broader verify workflow. This is insufficient for an agent to call it confidently without further discovery.

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 compensate. It gives meaning to expectedText ('page source text') but says nothing about serverUrl, sessionId, or the non-obvious sourceEvidencePrefix. At least two required parameters remain semantically unexplained.

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') and states the resource ('navigation target') and the mechanism ('expected Appium page source text'). This makes the core purpose clear. However, it does not distinguish itself from the closely named sibling verify.assert_screen_contains_text, so an agent may struggle to choose between them.

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?

There is no guidance on when to use this tool instead of appium.assert_visible or verify.assert_screen_contains_text. The name implies a navigation-specific check, but the description does not state exclusions, prerequisites, or alternatives. An agent is left to infer usage from sibling names alone.

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