Get media time

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

With no annotations, the description carries the full burden of behavioral disclosure. It accurately describes the read-only nature of the operation, but does not provide details such as time units (seconds/milliseconds), behavior when the source is missing, or whether any state is affected. This is a simple getter, so minimal disclosure is acceptable, but more context would improve transparency.

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, direct sentence that front-loads the action and outcome. There is no wasted text or redundancy, making it highly concise and well-structured.

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?

The tool is simple with one parameter and an output schema, so the description need not explain return values. However, given the lack of annotations and low schema coverage, the description should provide more context about time units or edge cases to be fully complete. It is adequate but leaves clear gaps.

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 schema has no descriptions (0% coverage), so the description must compensate. It mentions 'media source,' which hints that source_name identifies the media source, but it does not explicitly map the parameter or add format details. The schema's title 'Source Name' already provides some meaning, and the description adds only marginal context.

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 the tool retrieves the current playback position and duration of a media source. It uses a specific verb ('get') and resource, and distinguishes itself from siblings like set_media_time by focusing on reading rather than modifying.

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 implies usage for reading playback state, and the presence of set_media_time as a sibling clarifies when not to use this tool. However, it does not explicitly name alternatives or state exclusions, so it misses full marks.

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