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

Annotations already establish readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful return-style detail: summarised, cited insights from a curated knowledge base of practitioners, books, and research. It does not cover rate limits, but the email parameter schema covers tier access, and there is no contradiction.

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 compact sentences with each clause adding distinct value: domain scope, source type, and output style. No filler, and the content is front-loaded.

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 read-only knowledge specialist with three well-documented parameters, the description covers purpose, domain scope, and return shape (summarised, cited insights). The lack of an output schema is partly mitigated by the explicit return description; an explicit rate-limit or sourcing caveat would be a small improvement.

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 fully documents query, email, and top_k. The description only implies that query is a natural-language marketing question and adds no format, default, or constraint details beyond the schema, so baseline 3 is appropriate.

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?

States a specific action ('Ask') and a named specialist, scoped to local SEO, small-business marketing, and community presence. This distinguishes it from generic ergora_marketing and other siblings, though it does not explicitly name alternatives.

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 topic phrase implies when to use it — for local marketing questions — but there are no explicit 'use this instead of ergora_marketing/ergora_community' instructions or exclusions. An agent can infer the domain but gets no routing guidance among the many related siblings.

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