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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety and idempotence are covered. The description adds that the catalog content spans eval templates and OpenRegulatory-derived regulatory templates, which is useful scope context, but says nothing about catalog size, stability, or what a returned template record contains (no output schema exists to cover that).

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 well-formed sentence, front-loaded with the action and resource, with the examples earning their place by showing catalog breadth. Slight density from the 'from X to Y' construction but no waste.

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 read-only listing tool with full annotation coverage, the description supplies enough to select it correctly. The main residual gap is the nature of a 'brief template' and its return shape, though the latter is minor for a simple catalog read.

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?

Zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The description correctly implies no filtering or selection arguments exist.

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 — returns the catalog of brief templates Knos offers — and illustrates scope with two examples (AI model evals, regulatory milestones from OpenRegulatory). It implicitly separates itself from sibling knos_milestones (actual milestones) but never names or contrasts with any sibling explicitly.

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?

Reading 'returns the templates Knos offers' implies a discovery step before using knos_milestone_prompt or knos_milestone_submit, but the description never says when to call this versus those siblings or what to do with the result. Usage is inferable rather than stated.

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