node_find

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

No annotations are provided, so the description carries the full burden. It only states pagination but does not disclose important behavioral traits such as whether the search is recursive, how results are ordered, or performance implications. This is insufficient for safe autonomous use.

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 description is very concise, consisting of two short sentences. The second sentence is somewhat fragmented ('Filters AND together. Paginated.') but remains clear. Every word earns its place.

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?

Given that an output schema exists, the description need not detail return values. However, it omits whether the search is recursive (e.g., entire scene tree or only direct children). This is a notable gap for a search tool, making the description incomplete despite its brevity.

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 the schema already documents each parameter. The description adds 'At least one filter must be provided' and 'Filters AND together,' which provide context beyond the schema. Baseline 3 is appropriate.

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 function 'Find nodes in the scene tree by name, type, or group.' It uses a specific verb (find) and resource (nodes), and distinguishes from siblings like scene_get_hierarchy or node_get_properties by specifying the filtering criteria.

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 key usage constraints: 'At least one filter must be provided. Filters AND together. Paginated.' This tells the agent when to use this tool (need to filter nodes) and the combination logic. However, it does not explicitly state when not to use it or mention alternative tools.

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