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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral information: result ordering (newest first) and the exact record shape (id, paper or idea, verdict, report hash), which matters because no output schema exists. It does not say whether results are paginated or capped, which is the one real 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?

A single sentence with zero filler, front-loaded with scope ('Every crossing this server ran') followed by ordering and payload in a compact colon list. Nothing could be removed without losing information.

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 parameters, no output schema and rich annotations, the description covers what an agent needs: what is returned, in what order, and for which scope. The only omission, result volume or pagination behavior, is minor for a bounded per-server listing.

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 is nothing for the description to disambiguate; baseline 4 applies. The field list it does provide describes outputs rather than inputs, which is not a parameter-semantics contribution but also not a deficiency.

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 resource and scope: every crossing this server ran, with declared ordering (newest first) and returned fields. The verb is implicit ('ran' / listing) but the scope phrase 'this server' clearly separates it from knos_cross, which presumably executes a crossing rather than listing them. It stops short of naming that sibling, so it is clear but not fully differentiated.

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?

Usage is only implied: an agent can infer 'call this to review crossing history' but there is no explicit when-to-use, no when-not-to-use, and no pointer to knos_cross or knos_evidence as alternatives. For a zero-parameter list tool this is workable but leaves selection between knos_crossings and knos_cross to inference.

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