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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds that the result is server-wide and includes order and status, but says nothing about ordering of results, pagination, or what "held order" means.

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?

A single front-loaded sentence with no filler; the scope constraint and returned fields come before anything else.

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 simple read-only list with no params and no output schema, the description is close to complete, but the two return fields it names ("held order", "status") are left undefined, so the agent cannot interpret the response values without guessing.

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?

The tool takes zero parameters, so there are no parameter semantics to explain; the description correctly implies no filtering inputs. Baseline 4 applies for a param-less tool.

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?

It has a concrete verb and a scoped resource ("Lists every commitment on this server"), plus the returned fields (held order, status). But the resource is called a "commitment" rather than a milestone, and the title "Open milestones" conflicts with the description's "every commitment" on whether the list is filtered to open items, leaving the agent unsure what set is returned.

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?

There is no guidance on when to call this versus siblings such as knos_milestone_prompt, knos_milestone_submit, or knos_ready, nor any prerequisite or exclusion. The only usage cue is the implicit "on this server" scope, which the agent must infer.

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