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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description does add the useful behavioral fact that the call consumes a quota slot and a dispatch-ceiling reservation, which is real cost information not in the annotations, but it never quantifies the cost or explains what happens when the quota is exhausted.

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?

It is a single sentence with no filler and the action is front-loaded, which is good. However, the density of undefined internal jargon ('keyed tier-quota slot', 'dispatch-ceiling reservation') makes the sentence hard to parse without adding proportionate clarity.

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 notes it returns evidence and explicit gaps, which is helpful. But for a tool whose two parameters are entirely undocumented and whose quota/ceiling mechanics are opaque, the definition leaves meaningful gaps an agent would need resolved before a confident call.

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 0%, so the description must carry parameter meaning and it does not: 'niche' and 'question' are never defined, and the maxLength 2000 / minLength 1 constraints are undocumented. The ambiguous 'keyed' term might allude to the niche enum, but this is left for the agent to guess.

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 specific verbs (fetch, grade) and a concrete resource (studies from scholarly indexes), plus the return payload (fetched evidence and explicit gaps). It is distinguishable from the domain siblings like ecca_psychology or ecca_nutrition, though the jargon-heavy 'tier-quota slot and dispatch-ceiling reservation' framing muddies rather than clarifies the core 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?

There is no explicit guidance on when to select this tool over ecca_verify, ecca_synthesize, or the per-domain siblings (ecca_psychology, ecca_learning, etc.). 'Use one keyed tier-quota slot' hints at a cost/budget condition for invocation but never states the trigger or the alternative.

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