find_nodes

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

Discloses scoping constraint (current page) and default scope behavior, but no annotations exist to cover read-only or side effects. Does not state whether operation is safe or idempotent, leaving some behavioral ambiguity.

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 succinct sentences plus two examples. No wasted words. Purpose and critical constraint front-loaded immediately.

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?

Covers essential context: purpose, parameter defaults, page-scoping prerequisite. No output schema exists, so return format is not expected. Could mention case-sensitivity or partial matching, but overall adequate.

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?

Input schema already has full coverage (100%). Description adds value by clarifying scope default ('entire page') and providing a concrete node ID format example ('1:2'), which schema lacks.

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?

Description clearly states 'Search nodes by name or type' with specific verb+resource. Examples reinforce purpose. Distinguishes from sibling tools by explicitly noting scoping to current page and referencing switch_page for cross-page searches.

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?

Explicitly tells agent to call switch_page if target is on a different page, providing clear when-to-use guidance. Examples show typical usage patterns.

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