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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely new context: the reputation is "black-box" (the underlying computation is not exposed) and the response is scoped to tiers, tier gates, public profile identity, evidence, and freshness metadata, which tells the agent this is a shallow public view rather than a full scoring breakdown.

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, front-loaded with the purpose and then the return-scope constraint; no filler. The second sentence is dense but each clause carries distinct information, so it 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 read-only, single-parameter tool with rich annotations and an output schema, the core call information is adequate. However, the description describes return fields that the output schema already covers while omitting the one thing the schema and annotations cannot supply — how this differs from the other reputation tools and when to prefer it.

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?

Schema description coverage is 100%, and the single parameter already carries a pattern for the EVM address format, so the schema does the heavy lifting. The description only reinforces that the address is a counterparty wallet; it adds no format, chain, or validation detail beyond the schema. Baseline 3 for a fully documented single-parameter 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 pairs a specific verb ("Read") with a specific resource ("black-box public reputation for a wallet counterparty"), which is more informative than the tool name alone. It is clear what the tool fetches, but it never names or contrasts the adjacent reputation siblings (kellian_get_subject_reputation, kellian_get_agent_reputation, kellian_batch_counterparty_reputation), so the distinction rests on the word "counterparty" in the name and title.

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 explicit when-to-use, when-not-to-use, or alternative-selection guidance. Given that the sibling list contains at least four other reputation lookups (subject, agent, my, batch, leaderboard), the absence of any routing hint is a real gap; usage must be inferred from the name.

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