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

With no annotations, the description fully discloses behavioral traits: sentinel verification ensures the document was actually replaced, reloaded:false with a reason is returned if the reload failed, it waits for the new document to finish loading and reports ready, and hard:true bypasses cache. This exceeds typical descriptions by explaining the internal check and return semantics.

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?

Although dense, every sentence contributes meaningful detail: core action, cross-platform support, verification mechanism, return values, readiness behavior, iOS-specific rationale, and cache bypass. The structure is front-loaded with the action, then behavioral details, then context, with no wasteful filler.

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 description is complete: it explains return values (url, reloaded, reason, ready), the verification approach, the iOS use case, the difference from same-hash navigation, and the hard parameter. Given the tool's complexity and lack of an output schema, this description fully covers what an agent needs to invoke it correctly and interpret results.

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 100%, so baseline is 3. The description adds marginal value by mentioning hard:true, but that is already documented in the schema. It does not elaborate on udid, pageId, or socket beyond what the schema provides.

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 tool reloads the page in the device browser via CDP Page.reload, and explicitly notes it works on both iOS Safari and Android Chrome. It contrasts with sibling navigation/reload tools and emphasizes the forced real load vs. same-hash navigate, making its purpose distinct.

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?

The description provides strong usage context: it is the state-reset primitive between test cases on iOS, and explicitly distinguishes from a same-hash navigate by forcing a real load. It does not formally list alternatives or when-not-to-use, but the context is clear enough to guide agent selection.

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