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

readOnlyHint=true already covers the safety profile, so the description is free to spend its words on payload shape: each row carries application, on-screen menu path, opening capability, selection prerequisites, and the related guide. The pointer to /ai/ui-map.json usefully signals this is a static mirror of a known artifact, letting an agent skip the call if it already has that file.

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?

Two sentences, no filler. The scope constraint ('Every left-nav page of both signed-in applications') is front-loaded before the field list and the artifact reference, which is exactly the right order for an agent scanning for fit.

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?

With no output schema, the description correctly compensates by enumerating the returned fields, which is the most important gap to close for a list tool. Minor omissions remain: no mention of result volume, ordering, or how the optional application filter changes the payload.

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?

Single optional parameter with a fully documented enum and 100% schema coverage, so the schema does the work. The description only implies the default (both applications) and adds no filtering or ordering semantics beyond what the enum already states.

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?

Names the resource precisely — every left-nav page of both signed-in applications — and enumerates the per-page fields returned, so an agent knows exactly what comes back. The listing verb is carried by the name/title rather than the description, and differentiation from find_surface (single lookup) is only implicit.

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 implied usage — enumerate the whole nav map — is clear from 'Every left-nav page,' but there is no explicit statement of when to use this versus find_surface or get_guide. No prerequisites or exclusions are given; the agent must infer routing from the sibling names.

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