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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety/idempotency profile is covered structurally. The description usefully adds that the operation 'spends one solve' and runs a multi-step evidence/claims pipeline ending in a verdict, which reinforces the non-idempotent, resource-consuming nature. It stops short of explaining budget semantics, permissions, or what the verdict contains.

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 the domain front-loaded and no filler. The structure is efficient, though the second clause ('Applies evidence and claims checks; spends one solve') is telegraphic enough to be slightly cryptic.

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?

This is an open-world, multi-step tool with no output schema, yet the description never says what the verdict result looks like or what a 'solve' budget implies for retries. For a tool of this complexity, the description is materially under-specified.

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 the burden for the single 'question' parameter. It only alludes to 'the question' being refined, adding no format, scope, or length guidance beyond the schema's own min/max constraints, so it does not compensate for the coverage gap.

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 domain ('learning and study skills') and sketches a pipeline (refine the question, fetch studies, show named claims, render a verdict), so the general intent is inferable. However, it never states a crisp verb+resource and the phrasing is fragmented, so an agent cannot cleanly separate it from siblings like ecca_refine, ecca_research, or ecca_verify.

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 when-to-use, when-not-to-use, or alternative routing. 'Applies evidence and claims checks' hints at overlap with ecca_verify but gives no rule for choosing between them. The only usage signal is the implicit cost of 'spends one solve.'

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