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

No annotations are provided, so the description carries the full behavioral burden, yet it only lists output fields. It does not confirm the operation is a read-only aggregation, mention scope (global registry vs. filtered), or describe any behavioral traits; the 'get' prefix implies a safe read but nothing is disclosed explicitly.

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 compact sentence with the data source front-loaded, and no filler. However, it is written in Czech while the tool name and all sibling names are English, which adds a small parsing burden and is a structural inconsistency for an agent.

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?

An output schema exists, so the return values do not need explaining, yet the description spends its whole budget restating those return values instead. For a zero-parameter read tool this is minimally sufficient, but no usage context or scope information is provided.

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 the baseline is 4. The description correctly implies the summary is unfiltered and registry-wide, consistent with an empty argument object, and there are no parameter semantics to clarify.

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 data source (ERC-8004 ReputationRegistry) and enumerates the metrics the summary contains (feedback count, agents with reputation, unique clients, average score), but it never states a verb or that it aggregates the registry into a summary view. It is a noun phrase listing outputs rather than a clear statement of what the tool does, and it does not distinguish itself from check_wallet_reputation beyond the word 'summary'.

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 when-to-use guidance, no prerequisites, and no reference to any alternative. With siblings like check_wallet_reputation and get_trust_forensics present, an agent receives no signal about when the registry-wide summary is preferred over a per-wallet reputation check.

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