portkey-admin-mcp

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

No annotations are provided, so the description carries full burden. While 'Create' implies a write operation, the description doesn't disclose important behavioral traits like required permissions, whether this action is reversible (can collections be deleted?), what happens on duplicate names, or what the response looks like. For a creation tool with zero annotation coverage, this is inadequate.

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?

Two sentences, zero waste. The first sentence states the purpose, the second provides usage guidelines. Every word earns its place, and the most important information (what the tool does) comes first.

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 creation tool with no annotations and no output schema, the description provides good purpose and usage guidance but lacks behavioral context about permissions, reversibility, error conditions, or response format. The schema covers parameters well, but overall completeness is only adequate given the tool's complexity.

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%, so the schema already documents both parameters thoroughly. The description adds minimal value beyond the schema - it provides example values for the 'name' parameter (hourlink, apizone, research-pilot) but doesn't explain parameter interactions or provide context not in the schema. Baseline 3 is appropriate when 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 verb ('Create') and resource ('new prompt collection'), specifies the purpose ('organizing prompts by app'), and distinguishes from siblings by mentioning specific app names (hourlink, apizone, research-pilot) that aren't in the schema. This goes beyond just restating the tool name.

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 explicit usage guidance: 'Use one collection per app' with named examples (hourlink, apizone, research-pilot). This tells the agent when to use this tool (for organizing prompts by app) and implies when not to use it (don't create multiple collections for the same app).

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