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

With no annotations, the description does carry real load: it discloses the free quota (100/day per wallet, keyed by caller) and scopes the return to assessability only. It does not disclose what happens when the quota is exhausted, whether failures are distinguishable from 'not assessable', or the processing latency/limits, which are material for an unannotated tool with no output schema.

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 incentive ('FREE') front-loaded and no filler. The phrasing 'in the published submission form for one op' is dense jargon that costs a little readability, but nothing is wasted.

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?

It correctly fills the gap left by the absent output schema by stating what is returned ('assessability only'). Still, for a tool taking a nested artefact object and sitting beside evm/svm lint variants, an agent lacks the next-step guidance (what to call if the artefact is assessable, or what to do if it is not).

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 coverage is 100% and both parameters are already documented in detail, including the caller allowance keying and the EVM/SVM artefact forms. The description only adds the directive 'pass caller' and the constraint that the artefact covers 'one op', so it adds little beyond the schema; 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 operation ('headline pre-check') and its exact output ('whether the artefact is in the published submission form for one op'), which is far more specific than the tool name alone. It implicitly separates itself from linting siblings by stating 'no lint findings are returned', but it never names payload_preflight_evm, payload_preflight_svm or payload_preflight_criteria, so the reader must infer the routing.

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?

'FREE headline pre-check' plus 'no lint findings are returned' implies this is the cheap first gate before the full checks, and that deeper work belongs elsewhere. However, no alternative tool is named and no explicit when-not or prerequisite (e.g. which op families are supported) is given, so usage is inferred rather than stated.

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