get_scene_info

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

With no annotations present, the description carries the full burden of behavioral disclosure. The word 'ping' transparently signals a connectivity check and the phrasing implies a non-mutating read operation, but it does not disclose failure modes, whether the server must already be running, or any other operational traits.

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 tight sentence that front-loads the operation and enumerates the specific return fields without any filler. Every word earns its place, and there is no redundant information.

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 tool is relatively simple and the output schema exists to cover return values, but the description omits parameter semantics and does not differentiate sibling tools. It is adequate for a basic understanding, but not fully self-sufficient for an agent that needs to invoke it confidently without further inference.

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 0%, and the description does not mention command_id or idempotency_key at all. The parameter names hint at request tracking and idempotency, but no actual semantics are provided, leaving the agent without any explanation of how or whether these optional parameters should be used.

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 names a specific action ('ping' and 'return') and a specific resource ('scene information' including stage path, assets root, and prim count). It is clearly distinct from prim-level tools like get_prim_info or list_prims, though it does not explicitly name those alternatives.

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 about when to choose this tool over related siblings such as get_prim_info, list_prims, or get_runtime_status. The description implies it is for scene-level information, but it does not state when to use it or when not to, nor does it mention any prerequisites or exclusions.

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