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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose the return contents (score, tier, stats, flags), which is valuable, but it does not mention whether the operation is read-only, any side effects, or potential errors. Since it's a 'get' tool, the read-only nature is implied but not explicit, so a mid-range score is appropriate.

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?

The description is a single, front-loaded sentence that uses no unnecessary words. It effectively conveys the core function without redundancy, earning full marks for conciseness.

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?

There is no output schema, but the description compensates by listing the return components (score, tier, stats, flags). For a simple tool with one parameter, this covers the essential context. It is not exhaustive (e.g., no mention of error behavior), but it is adequate for the low complexity.

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 input schema already describes the sole parameter 'wallet' as 'Wallet address (0x...)' with 100% coverage. The description adds minimal new meaning beyond explicitly stating 'for a wallet address,' which is essentially the same. Since the schema does the heavy lifting, the baseline of 3 applies.

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 clearly states the tool's function with a specific verb ('Returns') and resource ('reputation score, tier, stats, and flags') for a wallet address. It is unambiguous and well-scoped, but it does not explicitly distinguish itself from sibling tools like get_agent_risk_score, so it falls short of a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention when it should be preferred over similar tools like get_agent_risk_score or get_attestation, nor does it state any exclusions or conditions. This is a clear gap.

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