resolve_get_current_page

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

No annotations are provided, so the description carries the behavioral disclosure burden. It transparently states that the tool returns the page name and lists all possible values ('media, cut, edit, fusion, color, fairlight, or deliver'). The word 'Get' also clearly implies a read-only operation with no mutation of application state.

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 efficient: one sentence states the action and result, and a second sentence lists the possible return values. There is no redundant information or filler.

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?

For a simple no-parameter getter, the description is fully sufficient. It names what the tool does and enumerates the valid return values, and an output schema is provided to confirm the structure. Nothing needed for correct invocation 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 tool has zero parameters, so there is nothing to document beyond what the empty schema already shows. The baseline of 4 applies because no parameter semantics are needed.

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 clearly states a specific verb ('Get') and resource ('currently active DaVinci Resolve page'), and explicitly enumerates the possible return values. It is easily distinguishable from the sibling resolver tools, especially resolve_open_page, which changes the page rather than querying it.

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?

The description makes the use case evident: call this when you need the name of the currently active page in DaVinci Resolve. It does not explicitly mention alternatives or exclusions, but for a read-only state getter the context is clear enough.

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