delete_printer_file

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

No annotations provided; description discloses destructive nature, confirm requirement, restricted directories, and path traversal rejection. Covers key behaviors well but could mention expected outcome or error cases.

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 efficient sentences: first states purpose and method, second adds critical behavioral constraints. No wasted words.

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?

Covers destructive nature, confirmation, directory restrictions, and path traversal. Missing return value description but overall adequate for a parameter-rich tool with no output schema.

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 has 100% coverage; description adds useful context like filename default directory and path format. Adds value beyond schema.

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?

Clearly states verb 'Delete', resource 'file from Bambu Lab printer's SD card', and method 'via FTPS'. Distinguishes from sibling tools like list_printer_files.

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?

Indicates destructiveness and need for confirm:true but does not explicitly state when to avoid or suggest alternatives. Usage context is implied but not fully elaborated.

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