hs4.admin.plugins.remove

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

With no annotations, the description must carry the burden of behavioral disclosure. It fails to mention destructive consequences, confirmation requirements, or the existence of safety mechanisms like dryRun and confirm parameters. Removal implications (e.g., data loss, service impact) are omitted.

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?

While the description is extremely concise (5 words), it sacrifices necessary details. It is appropriately front-loaded but fails to earn its place by providing minimal value beyond the name. A sentence slightly longer with key behavioral notes would improve it.

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 the tool has 10 parameters (2 required) and no output schema, the description is insufficient. It omits context about prerequisites (e.g., maintenance window, change tickets), expected side effects, and the role of dryRun/confirm. Sibling tools suggest a rich administrative context not addressed.

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?

The input schema covers 90% of parameters with descriptions. The description adds zero additional meaning beyond the schema. No parameter guidance, validation notes, or usage tips are provided, falling short of the baseline 3 for high schema coverage.

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 verb 'Remove', the resource 'plugin', and the context 'through admin controls'. It effectively distinguishes from sibling tools like install, update, set_enabled, and restart.

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 no guidance on when to use this tool versus alternatives such as hs4.admin.plugins.set_enabled or hs4.admin.plugins.restart. No scenarios or exclusions are mentioned.

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