itunes_get_position

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

With no annotations provided, the description must carry the full behavioral burden. It implies a read-only operation but does not explicitly state that no modifications occur, nor does it describe what happens if no track is playing or whether it returns null or errors. This lack of detail is a significant gap for a tool with no annotations.

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, concise sentence that delivers the essential information without any waste. It is well-structured and front-loaded, earning the highest score.

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?

Given the simplicity of the tool (0 parameters, no output schema), the description is minimally adequate. However, it lacks context about return format, error behavior (e.g., when no track is playing), and whether any permissions are required. An agent could use it correctly in a happy path but lacks guidance for edge cases.

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 the schema already fully covers the interface. The description does not need to explain parameters, and no additional parameter semantics are required. The baseline of 4 is appropriate here.

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 verb 'Get' and the resource 'elapsed time and total duration for the currently playing track.' It is specific and distinguishes from siblings like itunes_seek (which changes position) and itunes_current_track (which gets track info).

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?

No guidance is provided about when to use this tool versus alternatives. The description only states what it does, not when to use it or when not to. For example, it doesn't mention that itunes_seek should be used for changing position, nor does it mention any prerequisites like having a track playing.

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