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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: each rung carries an acceptance test that 'plain code will run on your output,' and passing means the work 'lands as a finding.' That is a real disclosure of the success contract, though pagination/limit behavior beyond the schema defaults is unaddressed.

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?

Front-loads the core operation and is tightly sized for a list tool. The shouty imperative and 'NEXT:' label cost a little polish but the sequencing information is useful, not filler.

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?

No output schema exists, so the description must convey the return shape — and it does, naming effort and the acceptance test per rung. Combined with annotations covering safety and the workflow pointing to read_rung/submit_rung, an agent has everything needed to call this correctly.

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 limit, offset, and effort. The description echoes effort filtering ('with its effort') but adds no format or bounds detail beyond the schema. Baseline 3 applies when structured fields carry the parameter burden.

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: 'Lists every open rung across all ladders with its effort and the acceptance test.' The content of each rung is described, and it clearly differs from read_rung, which it names as the next step. The leading 'FIND ONE SMALL, CHECKABLE PIECE OF WORK' is framing rather than a precise statement of the operation, keeping it just below a 5.

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 explicit workflow sequencing: use this to find a rung, then read_rung for the full spec, then submit_rung. That routes the agent correctly. It does not, however, contrast with sibling entry points like next_work or claim_work, so the 'when not to use' dimension is absent.

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