tdarr_delete_plugin

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

No annotations exist. Description only says 'Delete a plugin' without disclosing consequences (e.g., irreversibility, affected flows, or permissions needed). For a deletion operation, this is insufficient.

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?

Extremely concise at 3 words, with no unnecessary text. However, it could be more informative without sacrificing conciseness. Score 4 for efficiency but minimalism.

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 no output schema, no annotations, and a simple deletion operation, the description lacks context about effects, error conditions, or success confirmation. Completeness is low.

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?

Input schema covers all parameters with basic descriptions ('Plugin ID', 'Plugin source (local/community)'), so schema coverage is 100%. The description adds no extra meaning, meeting the baseline score of 3.

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 states verb+resource 'Delete a plugin', which is clear and distinguishes from sibling tools like tdarr_create_plugin or tdarr_read_plugin. However, it does not elaborate on scope or specifics.

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 guidance on when to use this tool versus alternatives like tdarr_remove_plugin_include or tdarr_delete_backup. No prerequisites or context provided.

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