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

There are no annotations, so the description carries the full burden of explaining behavior, but it only says to call it on a loop and then floor_home. It does not disclose what the tool actually returns, whether it is a read-only informational message, or whether repeated calls have side effects. The repeatability hint is useful but the behavioral picture remains thin.

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 short sentences with no filler. The key facts—that this is a 30-minute check-in, that it should be looped, and that floor_home follows—are all front-loaded and efficiently stated.

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-parameter tool with no output schema, the description is nearly sufficient: it tells the agent when to call it and what to do next. It does not describe the expected return payload, but the word 'instructions' implies the content, and the tool's simplicity lowers the need for more. The only notable gap is what the agent should do if the instructions differ across calls, but that is speculative.

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?

The tool has zero parameters and the schema has no properties, so there is nothing for the description to clarify. The baseline of 4 applies because parameter semantics are trivially complete. The description adds no parameter detail, but none is needed.

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 identifies the tool as '30-minute check-in instructions', which conveys the resource and schedule clearly enough. It lacks a strong verb like 'returns' or 'displays', but the phrase 'check-in instructions' plus 'Call this on a loop' gives the agent a usable sense of purpose. It is not a tautology and is distinguishable from siblings like floor_home by its periodic check-in role.

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 provides explicit operational guidance: 'Call this on a loop; then floor_home.' This tells the agent how often and in what sequence to invoke the tool, which is strong usage context. It does not mention alternatives or when not to use it, but for a zero-parameter heartbeat tool that is less critical.

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