ck_get_recent_transactions

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds almost no behavioral context beyond the annotations — it doesn't define what 'recent' means (ordering field), whether results are paginated, or what happens at the default limit, so it stays at the low end against an already-light bar.

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 short sentences, zero filler, with the core action front-loaded and the sibling relationship stated second. Nothing to trim.

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?

For a single-parameter read-only tool with no output schema, the description covers the essentials but leaves the notion of 'recent' undefined and says nothing about result ordering or shape. Adequate, but with clear gaps an agent must infer.

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 description coverage is 100% — the limit parameter is fully documented with default, range, and bounds. The description mentions 'N' but adds no syntax or format detail beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource (return the N most recent transactions) and explicitly relates it to the sibling ck_list_transactions as a shortcut. This lets an agent distinguish it from the general listing tool without opening either schema, though it doesn't clarify ordering or filtering differences.

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?

Calling it a 'convenience shortcut for ck_list_transactions' implies when to reach for it (quick recent-item retrieval), but it never states when to prefer the full tool instead or what the shortcut omits (filters, date ranges, pagination). Guidance is implied rather than explicit.

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