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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that tiers are 'public' and that 'method, period and completeness remain explicit', hinting at methodology metadata, but never states permission/auth needs, whether the data can be stale, or what happens on an unknown wallet. Adds modest context beyond annotations.

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?

Front-loads the resource and its contents, then the alternate mode, in three compact sentences with little waste. The sentence 'Method, period and completeness remain explicit' is slightly opaque, but no content is padding-level redundant.

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 an output schema present, the description needn't enumerate return shapes, and it covers the two call modes plus the field-level subject matter. The remaining gap is the address-vs-traderReference selection rule, which an agent must infer from 'Or'. For a two-param read-only lookup this is close to complete.

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 coverage is 50%: the EvmAddress definition documents the address format, but traderReference has only a regex and no description. The description partially compensates by explaining that traderReference yields 'a listed trader's lists and 3-month record'. It never says whether the parameters are mutually exclusive or that at least one is required (required count is 0), leaving the key usage rule unstated.

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?

Names a specific verb+resource and enumerates the returned fields (P&L by collateral, win/loss, win rate, markets traded, member-since), plus a second mode keyed on traderReference. It stops short of distinguishing itself from close siblings such as problee_get_counterparty_reputation, problee_get_subject_reputation and problee_get_forecaster_record, so an agent still has to guess which 'profile' tool to pick.

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 phrase 'Or a listed trader's lists and 3-month record by traderReference' implies a branch condition (wallet address vs. platform trader reference), which is useful. However, there is no explicit when-to-use/when-not guidance and no alternative tool is named despite five sibling reputation tools, leaving selection to inference.

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