KIROK_list_memories

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

No annotations provided, so description carries full burden. It discloses pagination behavior (limit, offset, defaults, max) and ordering, but does not mention side effects (read-only), performance, error handling, or what happens if bank_id is invalid.

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: two-line summary plus parameter list. Front-loads key info. Every sentence contributes value with no redundancy.

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?

With output schema existing, description doesn't need to cover return values. It adequately explains input parameters and pagination. Minor gaps: no mention of sort direction or behavior for empty results, but overall complete for a list tool.

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 0%, so description must add meaning. It does so by noting ordering ('most recent'), limit default and max (20, 100), and offset default (0), which are not in schema. However, it doesn't explain the bank_id parameter beyond its 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?

Description clearly states 'List memories in a bank with pagination, ordered by most recent.' It specifies verb (list), resource (memories in a bank), and key details (pagination, ordering). This distinguishes it from siblings like KIROK_get_memory and KIROK_list_banks.

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?

Usage is implied (browsing memories in a bank), but no explicit guidance on when to use vs alternatives (e.g., single memory retrieval or other list tools). No when-not-to-use or prerequisite conditions.

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