add_pdu

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

Annotations already establish readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds non-obvious behavioral context the annotations cannot convey: the mode-dependent execution timing (immediate vs. deferred until simulation_step). It does not say what state the PDU changes or how it appears in the simulation.

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?

Two tight sentences, no filler, with the core action front-loaded before the mode-dependent caveat. Every clause carries information an agent needs.

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?

With an output schema present, return values need not be described, and the mode-specific timing behavior is covered. The only remaining gap is that nothing states the effect (does it create a persistent object in the workspace?) or whether source/destination must be existing devices.

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 100% and both parameters (source, destination) are already documented with examples in the schema. The description conveys the 'one device to another' relationship but adds no format, naming, or edge-case detail beyond what the schema provides. Baseline 3 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?

States a specific verb and resource — 'Send a simple PDU (ICMP echo) from one device to another' — and anchors it to the familiar 'Add Simple PDU' UI button, so the agent understands exactly which capability this is. It does not name or contrast any sibling tool, so it stops short of the 5 tier.

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?

Explicitly describes the two usage contexts: it fires immediately in Realtime mode and defers to simulation_step in Simulation mode, which is genuine when-to-use guidance tied to sibling tools. It lacks any when-not-to-use or prerequisite statements.

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