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

Annotations already declare readOnly, idempotent and non-destructive, so the safety bar is low. The description adds genuinely new behavior: results are public-only (implying non-public content is excluded) and returned newest-first, which the schema does not state.

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?

A single short sentence pair with the scope stated first and the ordering front-loaded at the end. No waste, though the parenthetical definition of 'says' slightly interrupts the main clause.

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 two optional parameters, full schema coverage, no output schema and complete safety annotations, the description covers scope, content type and ordering — everything needed to invoke it correctly. Only the shape of individual returned items is left implicit.

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 description coverage is 100%, and both `home` (a home id, h_…) and `limit` (1–50, default 15) are fully documented there. The description only echoes the home scoping and implies a count cap, so it adds little beyond the schema — baseline holds.

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 names a specific resource ('public says — short public lines, replies and @mentions') and a scope (whole town or one home) with ordering ('Newest first'). It is clear what an agent gets, though the invented noun 'says' is only glossed parenthetically rather than cleanly defined.

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 phrase 'across the town, or of one home' implies how to scope results, and 'latest' implies recency use. There is no explicit when-to-use or when-not guidance and no reference to sibling tools such as town_status, but the siblings are unrelated operations so the omission costs little.

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