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

Annotations already establish readOnly/openWorld/idempotent/non-destructive behavior. The description adds meaningful context beyond that: it discloses an answer style ('summarised, cited insights') and source scope ('curated knowledge base of leading practitioners, books and research'). No contradiction is present.

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 sentences contain the action, domain scope, and return behavior with no filler. The most important query scope is front-loaded before the output description.

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 read-only research tool with one required natural-language parameter and no output schema, the description is complete: it says what to ask, what topics are in scope, and what kind of answer to expect. The absence of output schema is covered by the 'summarised, cited insights' clause.

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 explains query, email, and top_k thoroughly. The tool description adds no parameter-specific meaning, which is acceptable because the schema carries the full burden; baseline 3 applies.

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 names a specific action ('Ask') and resource ('the Ergora Community building ... knowledge base'), and further scopes it to brand communities, engagement, moderation, and events. It also states the output type (summarised, cited insights), making the tool's function clear and distinct from the other domain specialist siblings.

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 gives clear topical context for when to use the tool via 'brand communities, engagement, moderation, events', so an agent can route community-building questions here. It does not explicitly name alternatives or exclusion conditions, but the sibling list and domain are enough to imply the boundary.

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