pcb_delete_equal_length

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

With no annotations and a minimal description, the description fails to disclose behavioral traits such as irreversibility, required permissions, or side effects. The agent cannot determine what 'deleting' an equal length group entails.

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 extremely short but this is under-specification rather than conciseness. It lacks structure and does not effectively communicate 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?

Given only one parameter and no output schema, the description should provide complete context. It fails to describe what happens to the group (e.g., is it permanently removed?), associated traces, or any system effects. Incomplete for reliable tool invocation.

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% and the description adds no extra meaning to the 'name' parameter. The schema already labels it as '等长组名称' (equal length group name). Description does not enhance understanding.

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?

Description '删除等长组' translates to 'Delete equal length group', which essentially restates the tool name 'pcb_delete_equal_length'. It is a tautology, providing no additional clarity about the tool's purpose beyond what is implied by the name.

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?

No information is provided about when to use this tool versus sibling tools like pcb_delete_diff_pair or pcb_delete_keepout. There is no context for when deletion is appropriate or what prerequisites exist.

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