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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description usefully adds the nature of the response ("summarised, cited insights from a curated knowledge base"), but omits operational context such as the anonymous 5-query limit and the email-unlocked 30-query tier that only appear in the schema.

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?

Two tight sentences with the action front-loaded ("Ask the ... specialist") and the return behaviour second; no filler. It is efficient, though the second sentence could have carried a routing hint at no extra length cost.

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?

With no output schema, the description correctly compensates by stating that answers are summarised and cited. Combined with 100%-covered parameters and rich annotations, the only real omission is guidance on when to prefer this specialist over its siblings.

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 query, email, top_k and subscribe, including the tiering logic. The description adds no parameter-level meaning of its own, so the baseline 3 is the correct ceiling here.

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 states a specific verb ("Ask") and resource ("Ergora Community Building specialist") and scopes it with concrete sub-topics (brand communities, engagement, moderation, events), which naturally differentiates it from the other 18 domain siblings. It is clear, but it never explicitly contrasts itself with a neighbouring specialist (e.g. ergora_ask or ergora_marketing), so it falls just short of a 5.

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?

Usage is only implied: the agent can infer it should call this when it needs community-building expertise. There is no explicit when-to-use framing, no when-not condition, and no named alternative among the many sibling specialists, which is the exact ambiguity a routing decision needs resolved.

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