cleanBridgeBackups

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

No annotations are provided, so the description must fully disclose behavior. It says the tool deletes backup/duplicate files (destructive), but it does not state whether deletion is permanent, whether a confirmation prompt exists, what permissions are needed, or where the default scan occurs. This is a significant gap for a destructive tool.

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?

A single, front-loaded sentence that states the scan target, cleanup action, and user-visible benefit without any 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?

With no annotations, no output schema, and a destructive operation, the description should explain irreversibility, default behavior, and what 'scan' reports. It only provides the high-level purpose, leaving essential behavioral details missing.

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?

There is only one optional parameter (targetDir) with 100% schema description coverage. The description does not mention the parameter at all, but the schema already explains it clearly, so baseline 3 applies.

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 (scan and clean up) and resource (backup/duplicate jsx files in After Effects ScriptUI Panels), plus the user-facing consequence (Window menu clutter). No sibling tool performs this function, but the description does not explicitly distinguish it from siblings, so a 4 is appropriate.

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 implies when to use it—when backup/duplicate jsx files cause clutter in the Window menu—but does not explicitly state when to use it versus alternatives or mention any prerequisites or exclusions. Usage is inferable but not explicit.

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