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

Annotations already declare a safe, idempotent, closed-world read, so the safety profile needs no restating. The description does add real behavior beyond that: results include place-specific display names, roles, and pending join requests, and memberId values feed manage_member. It does not say whether results are paginated or how join-request entries differ from member entries.

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 short and front-loads the resource, but the closing clause 'Keep the names to the person' is cryptic and consumes space without adding usable instruction. Several phrases are terse to the point of ambiguity.

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 simple one-parameter read tool with no output schema, the description covers the main content categories (members, roles, join requests, memberIds). It falls short on return shape and ordering/pagination, which matter because there is no output schema to fall back on.

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?

There is a single parameter with full schema coverage that already explains it accepts a name or id and is omitted when the user has exactly one home. The description adds nothing further about the home parameter, so this is the baseline case where the schema carries the load.

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?

It conveys the resource (members of a place) plus extras (roles, pending join requests) and tags the memberId for manage_member, but the verb is implicit ('Who is in a place') and phrasing like 'named as the app names them there' and 'Keep the names to the person' is obscure rather than specific.

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 only implied: the agent can infer it should call this to see members and join requests, and the parenthetical 'with memberId for manage_member' hints at a follow-up tool. There is no explicit when-to-use vs. siblings such as list_friends, find_people, place_stats, or list_places, and no stated prerequisites.

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