workflows_featured_remove

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

With no annotations, the description carries full burden but only states 'Remove featured workflows,' failing to disclose whether removal is permanent, reversible, or requires specific permissions. No behavioral traits are clarified beyond the name.

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 sentence with no wasted words. However, 'Remove featured workflows' is almost too terse for a tool with required parameters and potential side effects.

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 is a mutation with one required parameter and no annotation coverage, the description is severely incomplete. It does not address return values, error conditions, or postconditions, which are essential for safe 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?

The input schema has 0% description coverage, yet the description adds no explanation for the 'workflow_ids' parameter. The parameter name is self-explanatory, but the tool description does not elaborate on expected format, constraints, or effects beyond the bare schema.

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' and the resource 'featured workflows', making the tool's action unmistakable. However, it does not differentiate from sibling tools like workflows_featured_add or workflows_featured_list, which share the same resource.

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 is provided on when to use this tool versus alternatives such as workflows_featured_list or workflows_featured_set. The description lacks context for appropriate invocation or prerequisites.

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