beacon_heartbeat

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

With no annotations, description discloses the heartbeat mechanism, time-to-live thresholds, and status transitions. Does not cover error handling or failure behavior, but overall transparent for the core function.

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 sentences: first states action, second provides essential timing details. No wasted words, perfectly front-loaded.

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?

Good for a simple tool with output schema present. Explains core purpose and timing constraints. Could mention what the response contains, but output schema covers return values.

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%, so description adds no additional parameter-specific meaning. The description contextualizes the parameters (e.g., status values), but the schema already documents each parameter well.

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?

Clear verb ('Send heartbeat') and specific resource ('Beacon relay agent'). Purpose is unambiguous and distinct from sibling tools like beacon_register (registration) and beacon_agent_status (status query).

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 required heartbeat frequency (every 15 minutes) and consequences of absence (60 minutes → 'presumed_dead'). Provides clear operational guidance without needing alternative comparisons.

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