portkey-admin-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It correctly indicates this is a destructive operation ('cannot be undone'), which is crucial context. However, it doesn't mention authentication requirements, rate limits, error conditions, or what constitutes a successful deletion. For a destructive tool with zero annotation coverage, this leaves significant behavioral gaps.

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 concise - just two sentences that communicate the core action and its irreversible nature. Every word earns its place with zero waste. The warning about irreversibility is appropriately front-loaded after the basic action statement.

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 destructive deletion tool with no annotations and no output schema, the description is incomplete. While it mentions irreversibility, it lacks crucial context about permissions needed, what happens to associated data, confirmation requirements, or what the response contains. The agent needs more guidance to use this tool safely and effectively.

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 description coverage is 100%, with both parameters clearly documented in the schema itself. The description mentions the 'slug' parameter but adds no additional semantic context beyond what the schema provides. The 'workspace_id' parameter isn't referenced at all in the description. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('Delete') and target resource ('a provider by slug'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from other delete operations in the sibling list (like delete_api_key, delete_collection, etc.), which would require mentioning what makes deleting a provider distinct from deleting other entities.

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. It doesn't mention prerequisites (like required permissions), when deletion is appropriate, or what happens to dependent resources. With many sibling tools including other delete operations and a 'get_provider' tool, this lack of comparative context leaves the agent without usage direction.

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