get_scene_info

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds that the tool returns object count, names, types, and locations, which is useful context. However, it does not mention performance, return format, or scope (e.g., all objects vs. selected), leaving some behavioral gaps.

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 a single, terse sentence. It is concise and front-loaded, but the Indonesian language may reduce clarity for non-Indonesian agents. Still, it contains no unnecessary words and delivers the core message efficiently.

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?

With an output schema present and no parameters, the description adequately covers the tool's purpose, specifying the key data returned (count, names, types, locations). However, it lacks guidance on how it differs from scene_summary or get_scene_graph, which would improve completeness.

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 tool has zero parameters, so there is no parameter information to document. The baseline of 4 applies, as the empty schema requires no explanation and the description correctly avoids parameter details.

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 the tool returns scene condition: number of objects, names, types, and locations. This is a clear resource, though it lacks an explicit verb like 'get' or 'list' and does not distinguish it from similar sibling tools such as get_scene_property or scene_summary.

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 get_scene_graph, get_object_info, or get_scene_property. The description only states what it does, with no contextual usage or exclusions.

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