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

With no annotations, the description carries the full burden and does meaningful work: it discloses re-verification against fresh on-chain state, the exact validation conditions (close targets must still be owner's empty accounts, fee must match rent), and that per-tx outcomes are returned. It omits irreversibility, idempotency/retry behavior, and auth requirements.

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?

Three tight sentences with zero redundancy; the submit action and the re-verification guarantee are front-loaded, and the return behavior closes the description. Every sentence earns its place.

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 mutation tool with no annotations and no output schema, the description covers the critical unknown (server-side re-validation before submission) and the response shape in general terms. Auth/fee-payer expectations and per-tx failure semantics are the remaining gaps.

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 already documents owner, signedTransactions, and lastValidBlockHeight with format and provenance detail. The description adds no syntax or constraint information beyond the schema, so 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?

States a specific verb (submit) plus the resource (reclaim-rent close-batch signed transactions) and notes the return of per-tx outcomes. It does not explicitly name solknife_reclaim_rent_build or _list, but the 'signed tx(s)' framing makes the execute-after-build role inferable.

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?

Implied usage only: the agent can infer this runs after /build because it accepts the signed transactions /build produced. There is no explicit when-to-use vs. _build/_list statement and no stated prerequisite ordering or failure handling guidance.

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