get_communities_v1_graph_communities_get

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It mentions 'public' and the return content (top datasets, topics), but does not disclose idempotency, pagination, rate limits, or sorting behavior. The description is insufficient for a read operation.

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 extremely concise, using a single line that includes the HTTP method and path. It has no unnecessary words, but the inclusion of the path may be redundant given the tool name. It could be more informative without sacrificing conciseness.

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 tool has no output schema and minimal inputs, so the description needs to cover response structure and usage details. It fails to explain pagination, sorting, or how to interpret the community listing. It is incomplete for a listing endpoint.

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 input schema has one parameter (limit) with 0% description coverage. The description does not mention this parameter or add any meaning beyond the schema, failing to compensate for the gap. It should explain that limit controls the number of communities returned.

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 community listing with top datasets and dominant topics,' which is a specific verb-resource combination. Among sibling tools, it is distinct from get_community_datasets (which targets a specific community) and get_bridges (graph bridges), so differentiation is clear.

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 includes '(public)' indicating accessibility, but it does not explicitly state when to use this tool versus alternatives or provide exclusions. Usage context is implied as a general listing endpoint, but no direct guidance is given.

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