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

There are no annotations provided, so the description carries the full burden of behavioral disclosure. The description only repeats the tool name and billing rate, providing zero information about side effects, authentication, rate limits, or response behavior. This is completely inadequate for a search tool that likely makes network calls.

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 short, but this is under-specification rather than conciseness. The billing note adds no tool-usage value and is better suited for metadata. It lacks any substantive content, so it cannot be credited for being 'tight' when it fails to convey purpose.

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 the lack of annotations, no output schema, and no description of return structure or behavior, the description is completely inadequate. A search tool with three parameters and pagination is non-trivial, yet the description ignores all of this. The tool is unusable for an AI agent relying on the description.

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%, with detailed parameter descriptions for nsfw, query, and nextPage. Although the main description adds no parameter guidance, the schema already explains each parameter sufficiently. Per the rubric, the baseline is 3 when schema coverage is high, and the description does not need to add more.

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 is essentially a restatement of the tool name ('search-communities') plus billing information ('Billing per call: 1 Credits'). It does not explain what the tool does with the search or what resources it acts on. At best it's a tautology, offering no new semantic content about the tool's purpose.

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 guidance is provided about when to use this tool versus its siblings such as get_search_comments or get_search_media. The description lacks any context for when this tool is appropriate, prerequisites, or exclusions. No alternative tools are mentioned.

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