Check state

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

With no annotations, the description carries the full burden and does real work: it discloses the auto-discovery mechanism (walking the React tree for the react-navigation container ref), the precedence rule for globalThis.__RNE_ROUTE__/__RNE_NAV__, and the explicit failure mode (route null plus a hint explaining why). It stops short of describing read-only semantics or how many/which 'recent errors' are included.

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 payload summary is front-loaded in the first sentence, with mechanism and fallback following in descending priority. The parenthetical about globalThis is slightly dense but genuinely informative, and no sentence is 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?

There is no output schema and no annotations, so the description must define the response — it names the three components and the null-route edge case but never describes the actual shape (route object fields, store state serialization, error list size/format). Adequate for a call decision, incomplete for interpreting the result.

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?

The single parameter has 0% schema description coverage, so the description must compensate — and it does, explaining that `path` is an optional dot-path into the store state, which tells the agent both its purpose and that it can be omitted. It does not state the default (whole store) or the path syntax, keeping it below a 5.

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?

States a specific action (one-shot snapshot) and enumerates exactly what it returns: current route, store state at an optional dot-path, and recent errors. This is far more concrete than the sibling names get_state/get_errors, but the description never names those siblings or explains how this combined snapshot differs from calling them separately, leaving differentiation to inference.

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 word 'one-shot' plus the combined payload imply this is the quick triage call rather than a targeted getter, and it notes no app-side setup is required. However there is no explicit when-to-use/when-not guidance and no mention of alternatives like get_errors, get_state, or observe, so routing between them is left implied.

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