locate_device

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

The description explicitly labels the operation as mutating, discloses that the LED state is persisted on the console, and assures that only the LED state changes without affecting connectivity or config. This goes well beyond the idempotentHint annotation and gives the agent a precise model of side effects.

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 front-loaded with the core purpose and follows with concise behavioral context. The Args section is somewhat redundant with the schema, but it is clearly formatted and not wordy.

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 description fully covers the operation's effect, persistence, parameter meanings, and scoping options. There is no output schema, but the behavioral outcome is clearly stated, and the tool is simple enough that no further detail is needed.

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 the Args section largely duplicates the schema's parameter descriptions. No additional semantic nuance is added beyond what the schema already provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Enable or disable LED blinking to physically locate a device.' It clearly identifies the tool's function and distinguishes it from sibling device-management tools like restart_device or upgrade_device.

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 purpose statement implies the usage context: physically locating a device. It tells the agent this is a locator function, not a general device management operation. It does not explicitly name alternatives or exclusion conditions, but the intended use is clear enough.

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