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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuine value beyond that: results are ordered largest-first, the return payload includes per-component size, bank counts and member samples, and it names the underlying FalkorDB primitive (algo.wcc).

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 dense sentences, front-loaded with the computation and followed by the output and parameter hints; no filler. The telegraphic, jargon-heavy phrasing ('triage clears instantly', 'algo.wcc') costs a little readability but not correctness.

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 no output schema, the description usefully summarizes the return payload and ordering, which is exactly what the agent needs. The only real gap is the undocumented 'limit' parameter for a tool that is otherwise well covered.

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 description coverage is 0%, so the description carries the burden. It does document the accepted 'graph' values ('consortium', 'bank_<id>', 'case_<id>'), which is real added meaning, but the 'limit' parameter is never explained beyond the implicit largest-first 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 description names a specific algorithm and resource ('weakly connected components of the transfer graph') and enumerates the output shape (size, bank count, sample members, tiny-island count), so an agent knows exactly what this computes. It does not explicitly distinguish itself from graph-analysis siblings like find_rings or top_hubs, though the algorithm name implicitly separates it.

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 mention of tiny 'islands' that 'triage clears instantly' hints this is a triage/orientation tool, but there is no explicit when-to-use statement or named alternative such as find_rings or account_network. An agent must infer the context.

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