Heartbeat protocol

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

With no annotations, the description reveals the tool returns a versioned playbook, implying read-only behavior. It could mention lack of side effects or required authentication, but for a simple tool it is adequate.

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 two concise sentences with no superfluous information, effectively conveying purpose and usage in minimal space.

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 zero parameters and no output schema, the description covers the essential behavior and usage. It could mention what the playbook contains or that it is cacheable, but it is complete enough for a simple protocol 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% with zero parameters, so the description does not need to add parameter details. Baseline 3 is appropriate as it neither adds nor detracts.

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 it 'Returns the canonical UnClick AI Seat heartbeat playbook,' specifying both the verb and the resource. It is distinct from sibling protocols like 'commonsensepass_protocol' by its focus on heartbeat.

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?

Instructions are explicit: 'Call this first from scheduled heartbeat seats, then follow the returned versioned procedure exactly.' It provides clear context and order of operations, though it does not list when not to use.

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