athena_retrieval_recent

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

With no annotations available, the description carries the burden. It discloses one key behavioral trait (no payload expansion) and mentions persistence, but does not describe ordering, return fields, or whether the list is limited to a particular scope beyond 'recent.' It adds some useful context but is not comprehensive.

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?

A single, front-loaded sentence that immediately states the action and resource. No wasted words, and the qualifier about payloads is efficiently included.

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 the tool's simplicity (one optional parameter, no output schema), the description adequately covers the core purpose and a key limitation. It does not fully explain behavioral details like the meaning of 'RAGRUN receipts' or ordering, but for a straightforward listing tool, it is reasonably 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?

Schema description coverage is 0%, and the description does not mention the 'limit' parameter at all. The schema offers basic type and min/max constraints, but the description provides no additional meaning for the parameter, failing to compensate for the lack of schema descriptions.

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 ('List') and identifies the exact resource ('recent persisted RAGRUN receipts') with a distinguishing qualifier ('without expanding full candidate payloads'). This clearly separates it from siblings like athena_retrieval_get and athena_retrieval_replay.

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 'without expanding full candidate payloads' implies when not to use this tool if full payloads are needed, but no explicit alternative is named. Clear context is provided for listing recent receipts, yet there is no direct comparison to sibling tools.

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