create_puzzle_switch

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

Without annotations, the description explains the switch activates a game switch and the door opens when ON, and that it creates 2 events. It covers core behavior but lacks details on permissions or what happens if the game switch ID is already used.

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?

Three sentences, each adding unique value: purpose, behavior, and creation count. No unnecessary words or redundancy.

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?

No output schema, so description should explain return values. It only says 'Creates 2 events' without specifying what is returned (e.g., event IDs). Also missing constraints like map existence or position validity.

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%, so baseline is 3. The description adds context by explaining the relationship between switch and door (switch activates game switch, door responds), which goes beyond individual param 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 clearly states the tool creates a puzzle switch and door pair on a map, using the verb 'Create' and specifying the exact resource. It distinguishes from siblings like create_chest or create_npc by describing a specific puzzle mechanism.

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 when placing a puzzle switch/door, but provides no explicit guidance on when to use this tool versus alternatives (e.g., create_teleport_event or create_chest) or when not to use it.

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