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

With no annotations, the description must carry the full behavioral burden. It does disclose return content fields and one business rule (locked milestones require an evidence page), which is real added context, but it omits any read-only/reversibility statement, ordering, or result-size behavior for what is implicitly a full-server listing.

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?

Two short sentences with no filler, and the resource is front-loaded. But the compression creates ambiguity — "every commitment" and "a locked one" require the reader to guess at entities and status semantics, so brevity costs clarity.

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 zero-parameter listing tool with no output schema, the description must explain the return shape. It names a few fields but does not describe structure, cardinality, or what the status values / claim id mean, so it is only partially complete.

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 per the rubric the baseline is 4. Nothing in the description conflicts with the empty schema, and no parameter meaning needs compensation.

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?

The description identifies the resource ("every commitment on this server") and enumerates returned fields (escrow order, units, status, claim id), so an agent can infer this is a listing tool. However it never states a verb and does not differentiate itself from close siblings like knos_tasks, knos_task_submit, or knos_evidence, leaving the scope of "commitment" vs "task" ambiguous.

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 explicit when-to-use, no when-not-to-use, and no named alternative among the many knos_* siblings. "A locked one needs an evidence page" is an oblique hint toward knos_evidence but is too cryptic to function as routing guidance.

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