agent_heartbeat

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

No annotations provided, so description bears full burden. It discloses the 5-minute timeout and the consequence (agent considered dead, appears in watchdog_check). Does not detail idempotency or side effects, but for a heartbeat the described behavior 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?

Two sentences, front-loaded with purpose, minimal waste. Every sentence adds necessary context (purpose, frequency, consequence). Excellent conciseness.

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?

With output schema present, return values need not be explained. Description covers purpose, usage frequency, and timeout consequence. Lacks prerequisites (e.g., agent registration) but overall complete for a simple heartbeat 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?

Input schema covers all 3 parameters with descriptions (100% coverage). Description adds no additional meaning beyond the schema. Baseline 3 is appropriate as schema does the heavy lifting.

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?

Description clearly states the verb 'report' and resource 'heartbeat' with specific purpose of maintaining liveness. It distinguishes from sibling watchdog_check by mentioning it, but does not explicitly differentiate from other agent-related tools like agent_activity_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 advises calling periodically to maintain liveness and explains the consequence of missing heartbeat (dead agent appears in watchdog_check). Does not provide when-not-to-use or alternatives, but context is clear enough for periodic signaling.

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