get_v1_bittensor_derivatives_wallet_ss58_reputation

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

No annotations are provided, so the description carries full burden. It mentions the data source ('independent full event archive') and the informational nature, but does not disclose whether the operation is read-only, potential side effects, or the response format beyond listing components. An output schema or more explicit behavior description would improve this.

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 concise, front-loaded with the core purpose, and includes necessary disclaimers and metadata (price, category) without superfluous information. Every sentence adds value.

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?

The description covers the tool's purpose, components, use case, and nature of data. However, given the lack of an output schema, more detail on the response structure would be helpful for complete understanding. The inclusion of 'formula disclosed' adds transparency.

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 has 100% coverage with a description for the `ss58` parameter. The description adds little beyond calling it a 'Bittensor address', which aligns with the schema. The schema's example mentions BTC, ETH, SOL, which may be inconsistent, but the description does not clarify further. Baseline 3 is appropriate.

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 provides a reputation verdict for a Bittensor address, detailing components like registration track-record, stake-behavior, longevity, and stability score. This distinguishes it from sibling tools that focus on subnet-specific metrics, prices, or other blockchain derivatives.

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 explicitly states the use case: 'Counterparty due-diligence for OTC, delegation, and subnet operators.' This gives clear context on when to use the tool. However, it does not mention when not to use it or explicitly compare with alternatives, which would have earned a 5.

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