playback_get_page

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

The annotation readOnlyHint=true already signals this is a read-only operation. The description adds value by enumerating all possible return values (pages) and the edge case where an empty string is returned if Resolve cannot determine the page. This provides useful behavioral detail beyond the structured annotation.

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 concise: a single leading sentence stating the purpose, followed by a compact list of possible return values. Every sentence earns its place, with no redundancy or unnecessary detail.

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 zero-parameter read-only getter, the description is complete. It fully specifies the return values, including an edge case, and given the existence of an output schema (as indicated by context signals), the description does not need to explain return structure further. The tool's simplicity means no additional context is required.

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 the baseline for this dimension is 4. The description adds no parameter information because none exists, and none is needed. The description focuses on output semantics, which is appropriate.

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 uses a specific verb 'Return' and a clear resource ('the name of the currently active Resolve page'). It is easily distinguished from sibling tools like playback_open_page, which implies setting or navigating to a page.

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 it clear this is a getter for the active page, but does not explicitly state when to use it versus alternatives such as playback_open_page. Usage is implied by the tool name and the list of possible return values, but no explicit 'when to use' or exclusionary guidance is provided.

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