tokledger_recent

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

No annotations are provided, so the description carries the full behavioral burden. It discloses ordering ('newest first') and a limit concept, but says nothing about read-only safety, authentication, pagination, rate limits, or what a 'ledger record' contains. For a data-retrieval tool with zero annotation coverage, this leaves significant gaps.

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?

The description is a single, front-loaded sentence with no waste. It communicates the core operation and ordering immediately.

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 no annotations, no output schema, and a 1-param schema fully documented, the description is minimally adequate. It omits read-only semantics, authentication needs, and return shape, which an agent might need for a ledger tool. It is complete enough to identify the operation but not to fully understand its behavior.

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%, so the schema already fully documents the 'limit' parameter (integer, default 20, range 1-200). The description adds the notion of 'N' but no syntax or default beyond the schema, so baseline 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 clear verb/resource: retrieve the most recent N ledger records. It distinguishes from siblings like tokledger_stats and tokledger_model_breakdown, which are aggregate-oriented, though it doesn't explicitly name an alternative. The purpose is clear without opening the schema.

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?

The phrase 'most recent N' and 'newest first' implies usage for recent activity, but there are no explicit when-to-use/when-not guidelines or named alternatives. The usage context is strongly implied by the description but not spelled out.

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