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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safe, deterministic, closed-world read profile is established without the description. The description adds that the content is 'public,' implying no authentication is needed, but discloses nothing further about response shape, size, or freshness.

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, and the subject (KME) leads. The only quibble is the repetition of 'public' and a slightly dense compound clause, but nothing needs trimming.

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 and no output schema, the description carries the full burden of explaining what comes back, and it only sketches this ('description' plus 'participation rules'). For a static documentation-style tool the definition is minimally adequate but leaves the agent guessing at the actual return content and formatting.

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 and the schema is effectively self-describing (additionalProperties: false, empty properties), so there is no parameter semantics for the description to add. The baseline for a 0-parameter tool is 4.

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 names a specific resource (KME) and enumerates its content: a public description plus public commercial participation rules. It also positions KME as 'one commercial venue within the broader KAI network,' which implicitly distinguishes it from the network-level overview tools. It stops short of explicitly contrasting itself with its obvious sibling, kai_overview.

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 statement of when to call this tool, no prerequisites, and no named alternative. The phrase 'within the broader KAI network' hints at a relationship to kai_overview and e2r_overview, but the description never tells an agent to prefer one over the other. Comparable to the MID calibration case, which scored 2 for the same absence.

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