search_scene

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

With readOnlyHint annotation already declaring safe-read status, the description adds meaningful behavioral context: the query language syntax, limit defaults (50, 0=unlimited), root scoping, and multi-scene filtering. These details go beyond the annotation and clarify how the search behaves.

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 concise and front-loaded: one sentence for purpose, then the syntax, followed by brief parameter explanations. Every line earns its place, and it is appropriately sized for the tool's complexity.

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 query syntax and all parameters, but does not describe the return format or ordering, which is notable given there is no output schema. However, the tool's purpose 'Search scene objects' implies the return of matching objects, and the given details are sufficient for most use cases.

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?

The schema provides no property descriptions (0% coverage). The description compensates fully by explaining the query syntax for the required 'query' parameter, and clearly describing 'root', 'limit', and 'scene' with defaults and meanings, adding significant value beyond the raw schema.

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 'Search scene objects' with a specific verb and resource, and immediately details the query syntax, making the tool's function unmistakable. It distinguishes itself from sibling tools like get_hierarchy or inspect by focusing on search-based filtering.

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 explains the query syntax and parameters, but provides no explicit guidance on when to use this tool versus alternatives like get_hierarchy or inspect. Usage is implied from the name and description, but there are no exclusions or alternative tool references.

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