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

Annotations already declare the non-read-only, non-idempotent, non-destructive profile, so the bar is lower. The description adds real behavioral context the annotations don't carry: a privilege requirement (SuperAdmin only) and an explicit confirmation guardrail (confirm:true), which is important for a state-changing tool.

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 compact fragments, front-loaded with the action and privilege constraint; no filler. The telegraphic style is efficient but slightly at risk of underspecification rather than deliberate concision.

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 output schema and 0% parameter documentation, the description covers who may call it, what changes, and the confirm guard, which is the minimum viable set. It leaves the identity parameters (farmId, ledgerId) and any post-write behavior unexplained.

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 0% across 5 parameters, so the description carries extra burden. It clarifies paymentReference, the single permitted status value ('paid'), and confirm:true, but says nothing about farmId or ledgerId beyond the loose phrase 'payout_ledger row'.

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+resource: marking a payout_ledger row as paid, with the paymentReference and the UI equivalent (Rent Admin Mark as Paid). It doesn't explicitly contrast with siblings like list_rentahatch_payouts, but the write-vs-read distinction is clear from the verb.

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?

Gives a prerequisite gate (SuperAdmin only) and a required invocation flag (confirm:true), which tells the agent when it is allowed to proceed. It does not name alternatives or describe when this should not be used (e.g., already-paid rows, other settlement paths).

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