athena_transport_recent

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

With no annotations available, the description carries the entire burden of behavioral disclosure. It implies a read-only list operation but fails to explain ordering, default time window, pagination, or any side effects. The minimal phrasing gives no insight into expected behavior beyond the literal action.

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 concise sentence with no filler. It is front-loaded with the verb and resource, and every word contributes to the core purpose.

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?

There is no output schema and no annotations, so the description should clarify what a 'transport receipt' is, what 'recent' means, and what the agent can expect in the response. The description is too sparse to support reliable invocation, especially given the large set of similar transport and *_recent sibling tools.

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 input schema defines a single 'limit' integer with min and max constraints but no description. The description does not mention the parameter or its effect on results. The name 'limit' is self-explanatory to some degree, but the description adds no semantic meaning beyond what the schema already provides.

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 recent AOR×Collective transport receipts, using a specific verb and resource. This distinguishes it from sibling tools like athena_transport_get (which likely fetches a single transport) and athena_transport_replay (which replays a transport).

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?

No guidance is provided on when to use this tool versus alternatives such as athena_transport_get or other *_recent tools. The description does not mention any context, prerequisites, or exclusions, leaving the agent without explicit selection criteria.

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