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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real context beyond that: it is a "mirror and never a leaderboard", data is shown "by feeling and count only", and output varies with connection state ("when connected as yourself"). It does not describe freshness bounds or pagination.

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?

It is a single dense run-on sentence listing four aggregates, followed by a list of example questions. The information is front-loaded but the framing ("as a mirror and never a leaderboard") adds prose weight before the concrete payload, and the one-sentence structure makes it harder to scan.

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 an output schema present the description need not document return values, and with zero parameters the input surface is trivially complete. It covers auth-state sensitivity and aggregation scope, but leaves ambiguous whether the parenthetical names are sub-sections of this response or separate tools to call.

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, so per the rubric the baseline is 4. There is no parameter syntax to clarify, though the parenthetical references to body_responding_today, family_carrying_today and prayer_in_place_totals are left unexplained about how they relate to this call.

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 (the family's activity today) and enumerates its constituent aggregates: people prayed for/encouraged, what the family is carrying, prayers at places, and Tables when connected. This distinguishes it from point-in-time siblings like tables_live_now or prayers_left_near. It does not directly name the siblings it is not, so it stops short of a 5.

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?

It supplies concrete trigger phrases in the user's own voice ("what is the family doing today", "is anyone praying right now", "what are people carrying"), which gives an agent solid context for when to call it. However, it never states when NOT to use it or names an alternative sibling for narrower questions.

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