Get User Activity

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states the action and does not address read-only nature, side effects, pagination behavior, or rate limits. The schema hints at pagination via limit/offset, but the description does not mention it.

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 directly communicates the core purpose without fluff. It is front-loaded and appropriately sized.

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 tool lacks an output schema and annotations, and the description does not clarify what 'trading activity' encompasses or how the data is returned. The information is minimal and insufficient for an agent to understand the full context, especially given the presence of overlapping sibling tools.

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 description adds meaning to the 'user' parameter by identifying it as a wallet address. However, with 0% schema description coverage, it should also explain the semantics of limit and offset, which are left implicit. Some added value, but incomplete.

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's function: 'Get trading activity for a wallet address.' It specifies a verb ('Get'), a resource ('trading activity'), and an object ('wallet address'). However, it does not distinguish from sibling tools like get_recent_trades or get_user_positions, which also retrieve trading-related data.

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 other similar tools. There is no mention of alternatives, prerequisites, or scenarios that favor this tool. Usage context is entirely absent.

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