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

With only a title annotation, the description carries most of the behavioral burden. It usefully discloses the 24-hour window and that each painting comes with available actions, but it does not explain authentication needs, result ordering, expiry behavior, or the response shape.

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 wasted words. It communicates the core scope and action hints efficiently.

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 simple, parameterless retrieval tool with no output schema, the description is largely sufficient. It explains what is returned and the timeframe, though it could say more about the exact shape or limitations of the results.

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 tool has zero parameters, so there are no parameter meanings to clarify. The description does not need to compensate for schema gaps, and the baseline for a no-parameter tool applies.

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 identifies a specific resource (paintings escaped with), a time window (last 24 hours), and the per-item action options (forge, sell). It is clearly a retrieval tool for recent heist loot, though it does not explicitly distinguish itself from siblings like my_collection or resell_artwork.

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?

Usage is implied by the focus on recent loot and the listed follow-up actions, suggesting it should be checked before forging or selling. However, there is no explicit when-to-use or when-not-to-use guidance relative to alternatives such as my_collection or the action tools.

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