List communities

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

No annotations exist, so the description is the sole disclosure. It does reveal account-scoping and the nested inclusion of linked groups, but says nothing about read-only guarantees, pagination, ordering, or response shape.

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?

One concise fragment without filler. It front-loads the core content, though a proper verb would make it a full sentence.

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 parameterless list tool, the description explains what data will be returned (communities plus linked groups) and its scope. The lack of an output schema is mitigated by this high-level return description, though details like field names are absent.

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?

Tool has zero parameters, so the schema already covers everything; the baseline for no parameters is 4. No parameter explanation is needed.

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?

States the resource ('communities') and scope ('this account belongs to'), plus the included nested data ('groups linked inside each one'). The verb is implied from the title, so the purpose is clear; it doesn't explicitly contrast with sibling tools like list_chats.

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?

No sentence tells the agent when to choose this over siblings such as list_chats or search_contacts. Use context is only implicit from the resource type, with no exclusions or alternative guidance.

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