discord_cleanup_download

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool cleans up files but doesn't explain what 'clean up' entails (e.g., deletion, archiving, moving), whether it's reversible, requires permissions, or has side effects. This leaves significant gaps for a tool that likely modifies system state.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every part contributing essential information.

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?

For a tool with no annotations, no output schema, and a potentially destructive operation ('clean up'), the description is insufficient. It lacks details on behavior, outcomes, error conditions, or integration with sibling tools like 'discord_download_attachment', leaving the agent with incomplete context for safe and effective use.

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%, with the single parameter 'path' documented in the schema. The description adds no additional parameter semantics beyond implying the path should point to a downloaded attachment, which is minimal value. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 action ('clean up') and resource ('previously downloaded Discord attachment file'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'discord_delete_message' or 'discord_clear_presence' that might also involve cleanup operations, missing full sibling distinction.

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 provides minimal guidance by specifying 'previously downloaded' files, implying usage after download operations. However, it offers no explicit when-to-use vs. alternatives, no prerequisites, and no context about when this tool should be preferred over other cleanup methods or tools.

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