kg_community

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

Describes the BFS algorithm and output grouping by distance. No annotations present, so burden is on description. It implies read-only operation but doesn't explicitly confirm non-destructive behavior or mention permissions.

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?

Every sentence serves a purpose: purpose, algorithm, use case, and parameter details. No redundant information, front-loaded.

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?

Covers purpose, algorithm, usage context, parameter format, and output structure (grouped by distance). With output schema present, return value details are not needed. No gaps identified.

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 has 0% description coverage; the description compensates fully with clear parameter definitions, including a concrete example for note_path and value ranges for depth.

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 clearly states the tool returns the connected cluster around a note using BFS flood-fill. It distinguishes from sibling tools like kg_paths by focusing on community detection rather than path finding.

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?

Provides context for when to use the tool ('useful for surfacing related concepts when working on a specific topic') but does not explicitly exclude other scenarios or mention alternatives like kg_paths.

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