ck_get_recent_transactions

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

Annotations already declare readOnlyHint=true, so no destructiveness caveat is needed; the description adds that results are the most recent N transactions. Annotations cover the safety profile, and the description adds modest behavioral context but no details about sort stability, side effects, or edges.

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 with no filler: the purpose statement leads, and the relationship to ck_list_transactions follows immediately. Every word earns its place.

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 one-parameter, read-only convenience tool, the description plus schema is nearly complete. It does not describe the return format, but since this is a shortcut for ck_list_transactions, the shape is implicitly inherited; an explicit note would make it fully complete.

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?

The only parameter, limit, is fully documented in the schema including its default (25), so the description has little to add. 'N most recent' does map meaningfully to limit, but the schema already carries the parameter semantics.

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 uses a specific verb-resource pair ('Return ... transactions') with a clear scope ('N most recent') and explicitly ties itself to ck_list_transactions as the broader operation, so an agent can tell it apart from sibling list/spending tools.

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 itself a 'convenience shortcut for ck_list_transactions' gives clear context that this is the quick path for recent transactions and names the relevant alternative. It stops short of explicit when-not-to-use conditions, but the shortcut phrasing implies when it is the appropriate choice.

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