sendPdu

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

With no annotations, the description carries the behavioral disclosure burden. It discloses the key side effect — 'Automatically enables simulation mode if not already active' — which goes beyond the input schema and helps agents anticipate system state changes. More detail about failure conditions (e.g., missing devices) would be useful but is not strictly necessary.

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 compact and front-loaded with the core purpose. The additional sentences about simulation mode and follow-up tools earn their place because they guide correct usage. It is not maximally tight, but it has no filler.

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?

The tool is simple with only two string parameters, and the description covers the creation action, the automatic simulation enabling, and the expected follow-up tools for result checking. In the absence of an output schema, the mention of getPduResults helps fill the result-reporting gap. It does not explain error conditions, but for this low-complexity tool the overall picture is complete enough.

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 sourceDevice and destinationDevice are already fully described as device names. The description adds no further parameter-specific meaning, but that is acceptable given the complete schema. Baseline 3 is appropriate here.

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 ('Add'), a specific resource ('ICMP ping PDU'), and the target ('between two devices'), making it clear what the tool does. It also distinguishes itself from sibling tools like stepSimulation and getPduResults by positioning them as follow-up steps.

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?

Provides clear operational guidance: it explains that simulation mode is enabled automatically and directs the agent to use stepSimulation and getPduResults for the full workflow. It does not explicitly mention when not to use this tool, but the intended usage context is sufficiently clear.

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