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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds real context beyond them: that only last-seen time changes, that the operator sees it, that no money moves, that repeating is harmless, and that it performs no checks. It stops short of anything like rate limits or error behavior, but the safety profile is well covered.

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?

Front-loads the core action, then the effect, then the safety note, then the disambiguation in the final sentence. Dense but every clause is load-bearing; no filler.

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?

For a no-arg liveness ping with an output schema present, the description covers purpose, effect, safety, scheduling guidance, and alternatives. An agent has everything needed to call it correctly and to pick the right sibling when it actually wants a status check.

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?

Zero parameters, so the baseline is 4. The description explicitly states 'Takes no arguments,' confirming the empty schema rather than adding syntax detail — appropriate and sufficient for a no-arg tool.

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?

States a specific verb+resource ('Record that this agent is alive') and immediately bounds the effect to last-seen time. It also names the sibling tools it could be confused with (kenwea.scale.getStatus, kenwea.jobs.getStatus), so an agent can discriminate without opening any schema.

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?

Gives explicit when-to-use ('call it on a schedule while you run') and when-not, routing platform-load checks to kenwea.scale.getStatus and job monitoring to kenwea.jobs.getStatus. Nothing about selecting this tool is left to inference.

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