get_v1_bittensor_derivatives_subnet_netuid_owner_reputation

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

With no annotations, the description carries the full burden. It adds behavioral context: 'Informational research data — not investment advice' and 'Price: $0.50', disclosing cost and advisory nature. It also mentions the data source is an independent event archive. Missing details on auth or destruction, but adequate given the informational nature.

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 three sentences, front-loaded with purpose and key details. Including 'Price: $0.50' and 'Category: bittensor-mantis' adds minor but useful context; could be trimmed slightly but remains efficient.

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 simple tool (1 param, no output schema, no annotations), the description covers purpose, usage, behavioral caveats, and cost. It is sufficiently complete for an agent to decide to use 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%, so baseline 3. The description does not add significant meaning beyond the schema's 'Path parameter netuid (e.g. BTC, ETH, SOL, or other supported identifier)'. It reuses similar examples but no new semantics.

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 retrieves a 'subnet-owner reputation verdict' detailing track-record, stake behavior, longevity, and multi-subnet footprint. It distinguishes from sibling tools by focusing specifically on owner reputation for a given subnet netuid.

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 a use case: 'Due-diligence before you stake, mine, or invest in a subnet.' However, it does not explicitly mention when not to use it or compare it to alternatives like wallet_ss58_reputation or other subnet-specific tools.

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