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

Annotations already declare a mutating, non-idempotent, open-world operation, and the description adds value on top: 'spends one solve' discloses a budget/resource cost the annotations do not, and the pipeline wording (refine -> fetch studies -> named claims -> verdict) reveals the internal stages. It still does not say what the verdict output looks like or whether the solve is consumed on failure.

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 domain front-loaded and no filler. The telegraphic phrasing ('spends one solve', 'Applies evidence and claims checks') is compact but borders on cryptic, slightly costing readability rather than adding bloat.

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 one-parameter tool with no output schema, the description covers the workflow and cost but omits what the verdict/result contains and how this composite relates to the refine/research/verify siblings. Adequate but with clear gaps for a tool an agent must choose correctly.

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% and there is a single required 'question' parameter, so the description must carry the load. Saying 'refine the question' merely echoes the parameter name and adds no format, length, or content guidance (e.g. that it is natural-language free text capped at 2000 chars).

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 concrete domain ('Money and business') and a sequence of actions (refine the question, fetch studies, show named claims before the verdict), so an agent can tell this is a domain-scoped question resolver. It distinguishes itself from generic siblings like ecca_refine/ecca_research by the money/business framing, though it never explicitly says it is not those tools.

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 'Money and business:' prefix weakly implies the domain in which to use it, but there is no explicit when-to-use, when-not, or named alternative among the ten siblings. With ecca_refine, ecca_research, and ecca_verify present, the agent is left to infer why this composite exists versus calling those steps directly.

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