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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: the result set contains rungs with their acceptance tests and a satisfied/open status. It does not mention pagination behavior despite limit/offset parameters, which is the remaining gap.

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?

Tight and front-loaded: purpose, domain definition, and routing in three short sentences with no padding. The all-caps hook is stylistically loud but does put the key idea first, and 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?

With no output schema, the description carries the return-content burden and does so by describing rungs, acceptance tests, and satisfaction status. Pagination semantics for a list endpoint are the one thing an agent must infer from the schema defaults.

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 limit, offset, state, and objectiveId are already documented in the schema. The description contributes nothing about these filters (e.g. that state accepts 'open'/'completed' or how objectiveId scopes results), so the 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 and resource ('Lists ladders') and immediately defines the domain concept: one hard problem split into rungs, each with an acceptance test that plain code checks. It also names the sibling tools it is distinct from (open_rungs, publish_ladder), so an agent can place it without opening a schema.

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?

The 'NEXT:' clause routes explicitly to open_rungs for the climbable subset and publish_ladder for creating ladders, giving clear conditions for choosing alternatives. It does not explicitly cover when to use this over read_rung for a single ladder, so the guidance is strong but not exhaustive.

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