airc_heartbeat

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

No annotations are present, so the description carries full burden. It states that the tool sends a heartbeat to maintain an online status, but does not elaborate on side effects or return behavior. For a no-parameter tool, this is adequate but minimal.

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, efficient sentence that conveys purpose and usage frequency with no wasted words.

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 a heartbeat tool with no parameters and no output schema, the description fully covers what the agent needs: it defines the action and the expected call interval.

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?

There are no parameters (schema coverage 100% on empty schema), so the baseline is 4. The description does not add parameter detail beyond the schema, but the usage guidance of calling every 30 seconds provides meaningful 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's purpose: sending a heartbeat to stay online, which is distinct from sibling tools like registration or message sending. It also specifies a clear frequency (every 30 seconds).

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 explicitly provides a usage guideline: call every 30 seconds. This gives clear context for when to use, though it does not discuss exclusions or alternatives, which are unnecessary for a simple heartbeat tool.

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