things_navigate

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

It adds important behavioral context beyond the annotations: the operation requires write permission despite being navigation, and it reports command acceptance rather than confirming creation or cross-device visibility. This meaningfully clarifies side effects and result interpretation without contradicting the annotations.

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 compact sentences with no filler. The main purpose is front-loaded, and the second sentence adds essential constraints without bloating the description.

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 covers the tool's general behavior and key limitations, and an output schema exists so return-value details are not required. However, with zero schema description coverage and nested parameter structures, it leaves the relationship between action, target, and list to inference, which is a meaningful gap.

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 carries the full burden for parameter meaning. It explains the high-level actions ('show', 'edit', 'quick_entry') and mentions items, built-in lists, and projects, but it never maps specific parameters like target or list to the described behaviors, and requestId remains 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 states a clear purpose: show a built-in list/item, open a task/project for editing, or show Quick Entry on this Mac. It names distinct resources and actions, though it does not explicitly differentiate itself from the similar-sounding sibling things_show_view.

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 implies when to use the tool: when the agent needs to navigate the Things UI or present Quick Entry. It adds a useful prerequisite (write permission) and a caveat that it only reports command acceptance, but it does not name alternatives or explain when to prefer another sibling.

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