Organize Music Files

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

Annotations already carry destructiveHint=true and readOnlyHint=false, so the safety profile is declared. The description adds value by suggesting dry_run for previewing, which is relevant to the destructive nature. It does not disclose that files are moved by default (copy_instead_of_move defaults to false) or what happens to already-organized files, but the annotation coverage lowers the burden here.

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 concise sentences with the core purpose front-loaded ahead of the dry-run tip. Every sentence earns its place and there is no filler, though the format enumeration could arguably have been trimmed without loss.

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 8 parameters, 3 enums, no output schema, and destructive default behavior, the description leaves the agent reliant on the schema for structure options, filename patterns, and response formats. The destructive-by-default move behavior and return value shape are not addressed, which matters given 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 description coverage is 88% (>80%), so the baseline is 3. The description adds minimal parameter meaning beyond 'based on metadata (Artist/Album)', which faintly maps to the structure parameter. With the schema already documenting most parameters, there is little room or need for description to compensate.

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: 'Organize music files into structured folders based on metadata (Artist/Album)'. The format list (MP3, FLAC, etc.) sharpens the scope and distinguishes it from siblings like organize_photos, though it does not explicitly name the generic organize_files alternative. Clear but not maximally differentiated.

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 one actionable usage hint—'Use dry_run=true to preview changes'—which is useful. However, it gives no when-to-use vs when-not-to-use guidance and does not name any alternative tool (e.g., organize_files, preview_organization), leaving the agent to infer the right choice among many organizer siblings.

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