detect_loot

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

With no annotations, the description carries full burden. It only states the basic purpose and does not disclose behavioral traits such as whether it requires a new screenshot, how results are returned, what happens when no loot is detected, or any limitations. The parameter 'fresh_screenshot' is mentioned in the schema but not in the description.

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 that effectively communicates the core purpose. It is front-loaded with the key information. However, it could be slightly more structured with additional details, but for its length, it is efficient.

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 has one simple boolean parameter and no output schema, the description is somewhat incomplete. It does not explain what the return format is, what happens when no loot is found, or how the 'fresh_screenshot' parameter affects behavior. While it covers the basic purpose, it lacks completeness for an agent to fully comprehend the tool's 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 coverage is 100% for the single parameter, so the baseline is 3. The description does not add any additional meaning beyond the schema's description of 'fresh_screenshot'. The parameter's role is already well-documented in the schema.

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's purpose: 'Identify ground items visible on the floor after a kill'. It uses a specific verb ('identify'), resource ('ground items'), and context ('after a kill'), which distinguishes it from siblings like 'analyze_inventory' (which analyzes inventory, not floor items) and 'detect_combat_state' (which detects combat, not loot).

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 description implies usage after a kill but does not explicitly state when to use this tool versus alternatives like 'analyze_screen' or 'find_object_on_screen'. No guidance on when not to use or trade-offs is provided.

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