godot_game_time

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

No annotations are present, so the description carries full responsibility. It mentions 'gated' but does not explain what gating entails (e.g., permission requirements or locking). The effects of actions like freeze/unfreeze or the exact behavior of step/step_until are not described, leaving behavioral impact unclear.

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 line, very concise, and front-loaded with the core concept. However, it uses abbreviations and compact notations (e.g., 'step(ms,inputs?)') that may hinder readability, and the term 'gated' is undefined.

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 complexity (2 parameters, no output schema, no annotations), the description is incomplete. It fails to specify the structure of the 'params' object, return values, side effects, or usage examples. The tool's behavior regarding the 'gated' constraint and the exact semantics of each action remain ambiguous.

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 coverage is 0%, so the description must compensate. It partially describes the 'action' parameter by listing possible values (freeze, unfreeze, step, step_until) and hints at sub-parameters for step (ms, inputs?) and step_until (condition, timeout_ms?, interval_ms?). However, the 'params' parameter is not explained, and the format for the action's sub-parameters is ambiguous due to question marks.

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 'Deterministic clock control (gated)' and lists actions (freeze, unfreeze, step, step_until), making the tool's purpose clear as controlling game time. It distinguishes from sibling tools which cover other Godot domains (editor, scene, node, etc.), but the term 'gated' is not explained, slightly reducing clarity.

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 or when not to use it. The description only lists possible actions without any context on prerequisites or exclusions.

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