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 safety profile is covered structurally. The description adds one real piece of context — that scoring internals are intentionally withheld — but says nothing about the shape or volume of what is returned, so it only modestly exceeds the annotation bar.

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, no filler, with the subject (what E2R is) front-loaded and the scope caveat trailing. Every sentence earns its place.

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 parameterless, read-only informational tool with annotations covering the safety profile, the description conveys what it covers and what it will not reveal. It could be slightly more explicit that the output is a static reference document, but nothing critical to invocation is missing.

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 has no parameters to document, so the baseline is 4. Nothing in the description conflicts with or needs to compensate for the empty schema.

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 the resource and its scope (the public purpose of the E2R protocol) and even expands the acronym into 'evidence-backed experience and reputation protocol,' which tells an agent the domain. It does not, however, distinguish itself from sibling overview tools such as kai_overview or kme_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?

'Public purpose' plus 'scoring internals are not public' implies this is an introductory read and explicitly rules out one use case (extracting scoring internals). No alternative tool is named for agents who need scoring details, so usage is only partially guided.

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