hyre-tvl

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

With no annotations, the description carries the full burden of disclosing behavior. It does not state whether the operation is read-only, what the 'trend narrative' entails, how the '$0.001' cost is applied, or any rate limits. The tool likely performs a read-only query, but this is not explicitly disclosed.

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 concise sentence that front-loads the core capability. The parenthetical '($0.001)' is an unexplained addition but does not bloat the text. It is appropriately sized and easy to scan.

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?

Given the lack of an output schema and annotations, the description is incomplete. It does not explain what the returned data looks like, what 'trend narrative' means, or how to interpret results. For a tool with optional parameters, more context is needed for effective use.

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 provides 100% coverage for both parameters ('chain' with default and description, 'limit' with description). The description adds the phrase 'across chains' which aligns with the chain filter but does not add new semantic meaning beyond the schema. 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 indicates the tool provides Total Value Locked (TVL) data across chains, which distinguishes it from sibling tools focused on tokens, wallets, or pools. However, it lacks an explicit verb like 'get' or 'retrieve,' and the phrase 'with trend narrative' is somewhat vague. Overall, it is understandable and distinct.

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 such as hyre-pools or hyre-yields. There is no mention of context, prerequisites, or exclusions. The sibling list exists but the description itself does not reference it.

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