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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral fact: the result set includes invited-but-not-signed-in people, not just authenticated ones. It does not disclose ordering, default page size behavior, or total counts, which the annotations cannot cover.

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?

One sentence, front-loaded with the verb and zero filler. It is appropriately sized but the terseness comes at the cost of the paging and targeting detail an agent would need.

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 paginated listing tool with no output schema, an agent needs to know how paging behaves and roughly what comes back. The description covers only who is listed, leaving pagination, result shape, and site identification unaddressed.

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 coverage is only 33% – only 'site' has a description – and limit/offset have no textual explanation anywhere. The description adds nothing about identifying the site, page size defaults (100), the 500 cap, or offset paging, so it fails to compensate for the low coverage.

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?

States a specific verb (List) and resource (people who signed in to or were invited to a site), and the parenthetical distinguishes visitors from members, which is the key ambiguity among the siblings. It stops short of naming list_members or invite_visitor, so it is clear but not explicitly differentiated.

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?

No when-to-use or when-not-to-use guidance is given. With siblings like list_members, invite_visitor, block_visitor, and remove_visitor in the namespace, an agent gets no explicit routing signal about which one to pick for which intent.

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