x_api_search_communities

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

With no annotations provided, the description carries full behavioral burden and succeeds by disclosing read-only risk, required OAuth tokens and scopes, environment-selection behavior, expected response shape, common failure conditions, and safety warnings about sensitive data. This is far beyond a minimal disclosure.

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 well-structured with labeled sections and front-loaded purpose. It is slightly verbose and includes a tautological 'Use when: Search Communities' line, but most sections earn their place given the tool's complexity.

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 tool with no annotations and no output schema, the description provides substantial context: auth prerequisites, environment selection, response wrapper, failure modes, and an example. However, it omits two parameters and gives only a generic response shape rather than community-specific fields, leaving some gaps for a 10-parameter tool.

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 schema has 10 parameters and 0% description coverage, so the description must compensate. It covers query, max_results, next_token, pagination_token, and environment-selection parameters, but it leaves authorizationKey and preferredAuthType undocumented. It also labels next_token and pagination_token as 'unknown,' which adds little semantic value beyond the schema.

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 opens with 'Search Communities,' a specific verb+resource statement that clearly identifies the action. It is distinguishable from siblings like x_api_get_communities_by_id, but it does not elaborate on what data is returned or how search results are scoped.

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 provides explicit usage guidance: 'Use when: Search Communities' and 'Do not use when... prefer x_schema_discovery or x_query_suggestion first.' It also lists recommended prerequisite and follow-up tools, giving clear direction on when to use this tool versus alternatives.

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