tpb_remove

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not state whether removal is permanent, if it cascades to associated data, or if any permissions are required. The word 'remove' implies a mutating action but lacks critical context.

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 filler words, making it concise and front-loaded. However, it could be slightly expanded to mention the 'slug' parameter without becoming verbose, which would improve completeness without sacrificing conciseness.

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 simple tool with one parameter, an output schema exists but no details are given. The description does not cover success/failure behavior, side effects, or return values. Given the lack of annotations and parameter explanation, the description is insufficiently complete for an AI agent to confidently invoke it.

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 one required parameter 'slug' with no description, and the tool description does not explain what 'slug' refers to. Since schema description coverage is 0%, the description should compensate by clarifying the parameter's meaning and format, but it does not.

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 'Remove a progress bar.' uses a specific verb ('remove') and a specific resource ('progress bar'), clearly distinguishing it from siblings like tpb_create, tpb_update, and tpb_increment. It is concise and unambiguous.

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. The description only states what it does (remove a progress bar) without any context about prerequisites, exclusions, or alternative deletion/finishing options like tpb_done.

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