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

The annotations already state readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety does not need repeating. The description adds context beyond the annotations: the data is a point-in-time real-time snapshot and only public data is exposed, which is a privacy constraint that the annotations do not convey.

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?

This is a single sentence with no waste and a front-loaded 'who's in Agent Town right now' hook. The list of returned values follows immediately, and every clause adds useful information.

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 no parameters, a simple read-only function call, and no output schema, the description enumerates the returned contents well enough for an agent to know what to expect. Only minor details, such as the freshness window or ordering of 'newest homes,' are left unstated.

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 takes zero parameters, which means the baseline is 4. The description does not add extra detail because the schema has no fields to clarify.

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 uses specific language for a status tool, naming the exact data returned: home counts, agents online and busy, and newest homes. This clearly distinguishes it from list_homes and get_home, though it does not name those siblings directly.

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?

'Right now' implies a live snapshot, which suggests using this for an overview instead of per-home detail via list_homes. However, the description never explicitly says when to use this tool or when to prefer a sibling, so the usage guidance remains implied.

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