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

Although annotations provide safety hints (readOnlyHint), the description provides critical structural transparency by detailing every field returned (e.g., 'trading pair, current dynamic fee floor in basis points, whitelist state'). This compensates for the missing output schema and is highly useful for agent execution.

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 dense but perfectly efficient. It front-loads the main function and then concisely lists all relevant data points returned in each entry, packing maximum information into minimal space.

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 that there is no defined output schema, the description is exceptionally complete. It thoroughly documents the structure, data types (basis points, TOR), and meaning of every piece of information the tool returns.

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 tool has no input parameters, meaning the description cannot add parameter semantics. Since the baseline score for 0 parameters is high, and the description is clear in its purpose, a 4 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 is highly specific, stating it 'Returns per-THORName dynamic L1 minimum swap-fee floors (ADR-026).' This clearly identifies the verb, the resource, and the scope, immediately differentiating it from other financial retrieval tools.

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 definition does not provide explicit guidance on when to use this tool versus alternatives. While its purpose is clear, the agent has no context on specific use cases or preconditions for invoking it.

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