get_now_playing

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

With no annotations, the description carries full burden. It correctly implies read-only behavior but does not disclose potential side effects (none expected), required conditions (e.g., a running MPRIS-capable player), or error states. Added detail on empty results or player absence 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 concise sentence that front-loads the core purpose. Every word adds value, with no redundancy 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?

Given no parameters and an existing output schema, the description provides enough context: it names the key fields (player, status, artist/title) and the underlying technology (MPRIS/playerctl). Could be slightly more explicit about platform assumptions (Linux with playerctl installed), but overall sufficient for a simple retrieval tool.

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 no parameters, so schema coverage is trivially 100%. The description adds no parameter information but also doesn't need to. Baseline for zero-parameter tools is 4.

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 current media information including player, status, and artist/title via MPRIS/playerctl. It distinguishes from the sibling 'media_control' which likely handles playback control. However, it doesn't specify what 'status' entails (e.g., playing/paused/stopped), so not a perfect 5.

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 retrieving current media state, contrasting with sibling 'media_control' for control actions. However, it lacks explicit guidance on when to use this tool versus alternatives, and does not mention prerequisites or cases where the tool might return empty.

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