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

With no annotations, the description carries the burden of behavioral disclosure. It goes beyond the name by revealing sort order, pagination behavior (echo nextCursor), limit range/default, and the exact row fields returned. This is meaningful behavioral context for an agent deciding whether the tool fits, though it stops short of discussing permissions or failure modes.

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 two tightly packed sentences: it front-loads the core operation and ordering, then lists the essential return fields and parameter constraints. Every clause earns its place, with no repetition of schema details or filler.

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 simple two-parameter list operation without an output schema, the description is complete: it specifies ordering, pagination behavior, limit constraints, and the fields present in each row. Nothing critical for an agent to call the tool correctly is missing.

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 description coverage is 100%, so the schema already fully documents both parameters. The description restates the limit range/default and cursor echo behavior, but adds no material semantics beyond the schema. Baseline 3 is appropriate because the schema does the heavy lifting.

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 uses a specific verb ('List') with a clear resource ('communities') and defines the ordering ('newest-first'), distinguishing it from single-community getters like get_community and other listing tools. Even without reading the schema, an agent understands exactly what resource and operation this tool covers.

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 makes the tool's basic use case obvious through the verb and resource, but it does not provide explicit when-to-use vs. alternatives. It neither names siblings like list_posts nor states exclusion criteria, so an agent must infer usage from the tool name and context.

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