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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context that annotations cannot express: output is auth-dependent, returning only 'the door' on the public endpoint versus the full live hall when connected as /me. The metaphor is opaque, but the disclosure itself is real and useful.

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?

Purpose is front-loaded in the first clause, but the second sentence ('the hall is seen from inside the family...') is metaphorical and takes effort to parse, and the closing sentence is a list of sample queries rather than tight specification. Some of this earns its place, some is stylistic padding.

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, return values need no explanation, and with zero parameters there is little schema surface to cover. The description supplies purpose plus the auth-dependent behavior nuance, which is the main thing an agent could get wrong. It is close to complete for a low-complexity read tool.

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 the schema carries no semantics to document and the baseline is 4. The description correctly avoids inventing parameters and instead describes what the caller receives.

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 states a specific verb+resource set: it returns live tables with host first name, gathering theme, seats, present attendees, and the Scripture on the table. That is concrete enough for an agent to know what comes back, but it never names or contrasts the obvious siblings (gatherings_tonight, events_this_week, communities_to_join), so the differentiation work is left to inference.

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?

Usage is conveyed only through example user phrasings ('is anyone gathered right now', 'where can I sit with believers tonight', 'a table about the Psalms'), which implies the trigger context well. There is no explicit when-not guidance and no alternative tool is named for near-miss cases like scheduled events or joining a community.

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