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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior context beyond that: membership is opt-in ('chose to publish'), and results include verification status and recent joins. It does not disclose ordering, pagination, or what happens when the limit is exceeded, and no output schema exists to cover those gaps.

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?

Two sentences, tightly written, with the population definition preceding the return-content statement in a logical order. Nothing is redundant, though the network-naming framing occupies space before the actual action is described.

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 read-only listing tool this covers the essentials: who is included and what is returned, with safety profile supplied by annotations. However, with no output schema and an undocumented n parameter, an agent still cannot know result ordering, default count, or pagination behavior before invoking.

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 single parameter 'n' has 0% schema description coverage and is never mentioned in the description, so its meaning (a result cap) and default behavior must be guessed from the name and the 1-100 bounds. The description's only hint is the vague 'recent joins,' which does not explain how n affects selection or ordering.

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 second sentence states the concrete action and return content: 'Returns members, their verification status and recent joins,' which lets an agent recognize this as a directory-listing tool. The opening sentence defines the population being listed (agents who published their public key), sharpening the resource. It stops short of a clear verb-first statement and does not distinguish itself from siblings like join_network or verify_log.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The only implied usage is browsing who is in the network, which an agent must infer from the phrase 'returns members.' With siblings such as join_network and verify_log available, this omission leaves routing ambiguous.

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