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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered externally. The description nonetheless adds real behavioral context by disclosing exactly which trades count toward the score and which are excluded, which the agent cannot infer from the schema.

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 front-loaded sentence with no filler; the qualifiers about on-chain and excluded trades earn their place by scoping the result.

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 no output schema, the description carries the burden of describing the return value, and 'reputation and dispute stats' is vague about shape and fields. It is adequate for a simple single-parameter read tool but leaves the response structure under-specified.

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 schema has zero description coverage for bot_id (only type integer, minimum 1), and the description does not mention the parameter at all. The phrase 'a bot's' only weakly implies bot_id identifies the target, so the single parameter's semantics remain largely undocumented.

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?

States a specific verb and resource ('Get a bot's ... reputation ... and dispute stats') and scopes the data precisely with 'verified on-chain trades only, linked/house trades excluded'. It is clear what is retrieved, though it does not explicitly differentiate itself from siblings like get_bot.

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 named alternative. Usage is only implied by the subject matter (assessing a bot's trustworthiness before trading), and the exclusion criteria hint at the intended scope rather than stating it.

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