get_scene_summary

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It simply states 'Get compact scene graph' without revealing whether it is read-only, the scope of the scene graph (current frame? entire scene?), or any side effects. The output schema exists but is not referenced.

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 concise at 4 words, which is efficient but omits critical information about parameters and behavior. It is not well-structured for an agent to understand usage.

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 the lack of annotations and minimal description, the tool definition is incomplete. While an output schema exists, the description does not clarify what the compact scene graph contains or how to interpret the results. Essential context is missing.

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 description fails to explain the single required parameter 'kwargs', which has no type or description in the schema. With 0% schema description coverage, the tool definition provides no semantic meaning for this parameter, making it impossible for an agent to know how to populate it.

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 'Get compact scene graph' clearly states the action (get) and the resource (compact scene graph), which is distinct from sibling tools like 'get_object_details' that provide specific object information. However, 'compact scene graph' is somewhat jargon-heavy and could be more explicit.

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_object_details' or 'get_blender_status'. The description lacks context on typical use cases or when a compact scene graph is preferable to other representations.

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