obs-get-transition-cursor

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

No annotations are supplied, so the description carries the full burden, and it delivers the most important behavioral facts: the value range (0.0-1.0) and the inactive sentinel (1.0). It does not cover whether this reflects studio-mode TBar position or only program transitions, or whether it is safe to poll, so it falls short of fully complete.

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?

One sentence, front-loaded with the verb and resource, with the essential range/sentinel detail in a compact parenthetical. Nothing is wasted and nothing important is buried.

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 no output schema, the description usefully characterizes the return value as a 0.0-1.0 number, which is the main thing an agent needs. For a zero-parameter getter this is nearly complete, though it omits how an active-vs-studio transition is distinguished and any error behavior.

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 is nothing for the description to disambiguate; baseline 4 applies. The schema is empty and 100% described, and the description correctly adds no redundant parameter talk.

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?

States a specific verb ('Gets') and a precise resource ('cursor position of the current scene transition'), which is unmistakably distinct from sibling getters like obs-get-transition-duration, obs-get-transition-kind, or obs-get-current-transition. An agent can tell exactly what it returns without opening the schema.

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?

Usage is only implied: the parenthetical '1.0 when inactive' hints this is for polling an in-flight transition, but the description never says when to call it versus obs-trigger-transition, obs-get-current-transition, or obs-get-tbar-position, nor any conditions to avoid it. Adequate as a hint, not as guidance.

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