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

Annotations already cover the read-only, non-destructive, idempotent profile, so the bar is lower. The description adds two valuable behavioral facts beyond the structured data: the SuperAdmin authorization requirement and the default masking of payoutDetails.details, which is important context for interpreting results.

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 terse sentences, front-loaded with the core action, with zero filler. Each sentence (what it lists, who can call it, what it masks) 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 read-only list tool with no output schema, the description covers safety and masking but omits any information about the four undocumented parameters and return/pagination behavior. Adequate but with clear gaps given the 0% schema coverage.

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% across 4 parameters (farmId required; limit, status enum, vendorFarmId), and the description names none of them. It mentions the masked field name but adds no meaning about filtering by farmId, vendorFarmId, status, or pagination via limit, so it fails to 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?

States a specific verb and resource ('List payout_ledger rows'), clearly identifying the tool as a read/list operation over payout ledger data. It is distinguishable from state-change siblings like update_rentahatch_payout_status, but does not explicitly name alternative list tools it might be confused with.

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?

'SuperAdmin only' communicates a clear access precondition, which is genuine usage information. However, there is no guidance on when to use this versus alternatives (e.g., update_rentahatch_payout_status or list_rentahatch_bookings), leaving selection largely to inference.

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