get_frame

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

No annotations are provided, so the description carries the full burden, and it does supply the key behavioral fact that the result includes both the frame number and FPS. However, it says nothing about whether 'current' means the playhead, the scene's frame range, or the viewport frame, and gives no side-effect or freshness guarantees.

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?

A single seven-word sentence with the object of the query ('current frame and FPS') front-loaded immediately after the verb. No filler, no restatement of the name.

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?

There is no output schema, so the description must convey the return payload, and it does name both returned values. It is adequate for a trivial no-argument getter, though it could say a word about frame-rate vs. scene FPS or units to be fully complete.

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 takes zero parameters, so there are no argument semantics to document; per the baseline for a 0-parameter tool, a 4 is appropriate. The description correctly implies this is a pure query with nothing to configure.

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 a specific verb and resource ('Get the current frame and FPS') and is distinguishable from siblings like set_frame and set_frame_range by the read vs. write framing. It does not explicitly name an alternative tool, so it stops short of a 5.

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?

There is no guidance on when to call this versus get_keyframes / set_frame / get_scene_info, nor any stated prerequisites or exclusions. The intended use (querying playback state) must be inferred entirely from the name and the word 'current'.

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