hl_user_twap_slice_fills

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

With no annotations provided, the description must fully disclose behavior. It merely restates the tool name with 'Recent TWAP slice fills' and gives no details about time windows, ordering, pagination, or what constitutes a 'slice fill'. This is essentially a tautology and adds no behavioral transparency.

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 extremely short, but that is under-specification rather than effective conciseness. It reads as a title or subtitle, repeating the tool name, and does not offer any additional information that earns its place. No clear sentence structure or front-loaded verb.

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?

Although the tool is simple with one required parameter and an output schema exists, the description lacks essential contextual information such as how 'recent' is defined, any default limits, or how this differs from other fill-related tools. The agent has no basis for deciding when to use it or what to expect.

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 0%, and the description does not compensate for the single 'user' parameter. It provides no context about what format the user should be in, whether it's an address, ID, or other identifier, or any constraints. The description adds no semantic value beyond the parameter name.

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 'Recent TWAP slice fills' clearly identifies the resource (TWAP slice fills) and implies a retrieval operation, distinguishing it from sibling tools like hl_user_fills. However, it lacks a specific verb like 'get' or 'list', and 'recent' is somewhat vague.

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?

No guidance is provided on when to use this tool versus alternatives such as hl_user_fills or hl_user_fills_by_time. The description does not mention any exclusions or preferred contexts, leaving the agent to guess when this specific tool is appropriate.

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