remove_egovframe_components

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

With no annotations, the description fully carries the burden. It discloses that only manifest-recorded files are deleted, refusal of dependent or hash-mismatched files by default, force creating backups in remove-backup/ with transactional removal, and dryRun preview support. This is rich, non-obvious behavior.

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, dense sentence that front-loads the core purpose and follows with safety and mode details. Every word adds value; no redundant or vague phrasing.

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 removal tool with four parameters and no output schema, the description covers the essential behavioral aspects: scope, safety guards, force semantics, and preview mode. It could mention what the tool returns (e.g., list of affected files), but that is a minor gap given the dryRun preview is already described.

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 coverage is 100%, so parameters are already documented. The description adds meaningful context by explaining how force and dryRun affect behavior (e.g., backup creation, transactionality), which goes beyond the schema's simple type/default descriptions.

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 uses a specific verb ('removes') and resource ('components assembled with add_egovframe_components'), clearly distinguishing it from sibling tools like add_egovframe_components and list_egovframe_components. The scoping to manifest-recorded files adds precision.

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?

It provides clear context for when to use the tool (to remove previously added components) and explains the default refusal behavior and force option. However, it does not explicitly name alternative tools or when not to use it, so it falls short of a perfect score.

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