get_bounding_box

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

No annotations are provided, and the description does not disclose whether this is a read-only operation, whether it modifies the scene, or any side effects. It is likely a query, but nothing in the description confirms this.

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 extremely short and contains no redundant words, but it lacks structure and detail. It is not well-organized to convey the tool's purpose or usage effectively.

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 is incomplete. It does not mention the output format, the behavior with multiple objects, the effect of the world parameter, or any error conditions. The tool's context is insufficient for an agent to use it 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?

The schema defines 'world' and 'objects' with types, but the description gives no meaning to them. The 'objects' parameter accepts string, array, or object, which is confusing and unexplained. Without semantics, an agent cannot correctly construct the input.

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 '合并包围盒：min/max/center/size' is vague. It mentions merging bounding boxes but does not clarify whether it computes the combined bounding box of multiple objects or returns the components for a single object. The list of min/max/center/size suggests a query, but the verb 'merge' is ambiguous without context.

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?

No guidance is provided on when to use this tool versus alternatives like measure_distance or other geometry queries. There is no mention of when the world parameter matters or how objects should be specified.

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