get_communities

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds 'Read-only' and describes the return format in detail: 'Returns JSON: { communities: [{ id, files, size }], total }'. This adds value beyond annotations. No contradiction with annotations.

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 short sentences, each serving a distinct purpose: first states the function, second gives prerequisite and output format. No wasted words. Front-loaded with key information.

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?

The description covers the purpose, prerequisite, safety (read-only), and return format. Given there is no output schema, describing the JSON structure is essential. All relevant context is provided.

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 tool has no parameters, and the schema coverage is 100%. With zero parameters, the description does not need to elaborate. A baseline of 4 is appropriate as there is nothing missing.

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 'Get previously detected communities (file clusters)', which identifies the verb and resource. It implies retrieving all communities, and mentions the prerequisite run of detect_communities. However, it does not explicitly distinguish itself from the sibling tool 'get_community' (singular), which likely retrieves 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 explicitly states 'Run detect_communities first', providing a clear prerequisite. It also notes 'Read-only', indicating when it is safe to use. However, it does not mention when not to use this tool or discuss alternatives like 'get_community'.

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