summarize_all_communities

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

No annotations are provided, so the description carries full burden. It mentions 'force' for regeneration, implying idempotency, but does not disclose potential long-running behavior, resource consumption, or side effects of batch operations.

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?

The description is concise, front-loaded with purpose, and uses a structured Args list without extra fluff. Every sentence adds value.

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?

Given 4 parameters and an output schema, the description covers parameter usage but lacks broader context like when to choose batch over single community summarization. Output schema exists, so return values are not needed.

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?

With 0% schema description coverage, the description adds meaning by specifying allowed values for 'level' ('macro'/'micro' or integer 1/2), 'concurrency' default 5, and 'force' boolean. However, it does not explain the difference between 'macro' and 'micro' or the format of 'comm_ids'.

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 '批量/并行生成社区摘要' (batch/parallel generate community summaries), specifying the verb (generate), resource (community summaries), and scope (batch/parallel). It distinguishes from the sibling 'summarize_community_v1' which likely handles a single community.

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?

The description implies use for batch summarization via the name and parameter 'comm_ids', but does not explicitly state when to use this tool versus alternatives like 'summarize_community_v1'. No when-not or exclusion criteria are provided.

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