pickup

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

Without annotations, the description fails to disclose behaviors such as what happens if the item is not present, whether the action can fail, or if it is destructive. The return value is minimally described as 'Pickup confirmation' without further detail.

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 short but includes redundant 'Args:' and 'Returns:' sections that echo the schema. It is not overly verbose, but some structure could be improved.

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 pickup tool, the description covers the basic purpose and parameter but omits important context like error handling or whether the tool consumes game actions. The return value is vague, and no output schema is provided despite the signal indicating one exists.

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%, forcing the description to compensate. However, it only repeats 'Item name to pick up,' adding no format, constraints, or examples beyond the schema's type string.

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 specifies the action 'Pick up' and the resource 'item or connector from the current room,' effectively distinguishing it from sibling tools like attack, examine, or use_item.

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 on when to use this tool versus alternatives (e.g., examine to check item presence). The description only mentions the context 'current room' but offers no exclusions or prerequisites.

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