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

No annotations provided, so description carries burden. Discloses authentication requirement and action types, but does not mention rate limits, data freshness, error handling, or behavior on invalid JWT. Moderately transparent.

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?

Single sentence front-loading purpose and key prerequisite. No wasted words; efficient and scannable.

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 100% schema coverage and no output schema, description covers authentication, pagination, and optional token filter. Adequate for a paginated list endpoint. Could mention that it returns action objects but schema already defines parameters.

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 coverage is 100%, baseline 3. Description adds context for JWT (linking to auth tool) and tokenAddress (optional filter), but defaults for page/limit are already in schema. Adds marginal value beyond schema.

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?

Clearly states verb 'list' and resource 'paginated action history' of an authenticated smart wallet. Distinguishes from siblings by mentioning authentication prerequisite and specific action types (transfers, contract calls).

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?

References prerequisite tool `fuse_smart_wallet_authenticate` and mentions pagination, but does not explicitly state when to use vs alternatives or when not to use. No exclusion criteria or alternative tool guidance.

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