Get vocabulary

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

Without annotations, the description covers key behaviors: additive-only sync, cursor pagination with limit up to 200, and grounding in listening history. Missing output schema details but adequate.

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?

Two sentences packed with information, front-loaded with core purpose, then usage and pagination. No fluff.

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?

Lacks explicit return schema, but mentions next_cursor and FSRS fields. For a list tool, more detail on response structure would improve completeness.

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?

Adds context beyond schema: 'since' as ISO 8601 from prior updated_at, 'cursor' as opaque, 'status' from FSRS, 'language' as ISO 639-1. Schema coverage is 83%, and the description fills remaining gaps.

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 lists the user's vocabulary aggregated per word with FSRS maturity details, distinguishing it from sibling tools like 'lookup_word' or 'list_library'.

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?

Explicitly explains when to use filters, incremental sync via cursor and since, and notes that full-resync is needed periodically. Does not compare directly to siblings but provides clear usage context.

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