Update my Now Playing status

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

No annotations provided, so description fully carries the burden. It discloses required agent_id, the optional next_checkin_at behavior with detailed explanation of display and MIA status, and that status persists until changed.

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?

Two efficient paragraphs: first covers core purpose and usage, second details the optional parameter. No fluff, every sentence adds necessary information.

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 output schema, description doesn't need to explain return values. It covers purpose, usage, parameters, and behavioral details comprehensively for a mutation 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?

Schema coverage is 100%, baseline 3. Description adds significant value: explains agent_id as stable identifier, status max 200 chars, and next_checkin_at thoroughly—ISO/duration formats, UI behavior, clearing with empty string.

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 updates the human's Now Playing status, using specific verb 'Update' and resource 'status'. It distinguishes well from siblings as no other sibling tool appears to set the human's status.

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?

Explicitly states when to call: 'Call when you start a task, change focus, or idle out.' Also explains persistence and the dead-man's-switch use case, providing clear context without needing alternative tools.

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