Search Scene

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

The annotation readOnlyHint=true already indicates a safe read operation, and the description adds behavioral details like 'root: scope search to subtree (path or None for whole scene)' and 'limit: max results (default 50; 0=unlimited)'. It does not discuss return format or error behavior, but the annotation lowers the bar and the added details are useful.

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 front-loaded with the purpose, followed by a compact syntax line and then brief parameter explanations. Every sentence earns its place, with no fluff or redundancy, making it highly efficient.

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?

For a search tool with no output schema, the description adequately documents the query syntax, all parameters, defaults, and special values (0=unlimited). It lacks explicit return-value details, but the read-only nature and clear invocation requirements make it sufficiently complete for an agent to use correctly.

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 baseline is 3. The description essentially repeats the parameter semantics found in the schema, though it adds the shorthand syntax summary (e.g., 'tag=Tag', 'layer=N') and clarifies 'multi-scene only' for the scene filter, which is a slight enhancement.

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 'Search scene objects' with a specific verb and resource, making the core purpose obvious. However, it does not explicitly differentiate itself from sibling tools like get_hierarchy or inspect, so it stops short of a 5.

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 usage through its query syntax and parameter explanations—use this when you need to find scene objects by name, component, tag, layer, or active state. It provides no explicit alternatives or when-not-to-use guidance, leaving the agent to infer context from the sibling list.

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