polymarket_get_user_activity

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds context by listing specific activity types (TRADE, SPLIT, etc.), enhancing transparency. Does not describe pagination or ordering but provides reasonable additional behavioral context.

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?

Highly concise: one sentence for purpose followed by a clear parameter list. No redundant or unnecessary information.

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?

Input parameters are well-covered, but given that an output schema exists (as per context signals), the description does not hint at the structure of returned data. For a user activity tool, knowing output fields (timestamps, market details) would be helpful.

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?

With 0% schema coverage, description compensates by explaining wallet as EVM address, limit as 1-100 with default 20, and type as optional with examples. Adds meaning beyond schema, though formal enum for type is missing.

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?

Description clearly states 'Recent on-chain activity (trades, splits, merges, redeems...) for a wallet,' providing a specific verb and resource. Distinguishes from sibling tools like polymarket_get_user_positions and polymarket_get_user_value by focusing on activity types.

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?

Implies usage for fetching recent activity but does not explicitly state when to use this tool versus alternatives like polymarket_get_user_positions or polymarket_get_user_value. No when-not or exclusions provided.

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