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 states the action ('retrieve') but doesn't cover critical aspects like whether this is a read-only operation, potential error conditions (e.g., invalid slug), authentication needs, rate limits, or the format of returned information. This leaves significant gaps for a tool that likely involves data access.

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, efficient sentence that front-loads the core action ('retrieve detailed information') without unnecessary words. Every part of the sentence contributes directly to understanding the tool's purpose.

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 complexity of a retrieval tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits (e.g., read-only nature, error handling) and doesn't explain what 'detailed information' includes, leaving the agent uncertain about the tool's full context and output.

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 description adds minimal value beyond the input schema, which has 100% coverage. It mentions 'by its slug' to clarify the parameter's role, but the schema already describes 'slug' as 'the unique slug identifier of the integration to retrieve.' This meets the baseline since 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 verb ('retrieve') and resource ('detailed information about a specific integration'), making the purpose explicit. However, it doesn't differentiate from sibling tools like 'get_integration_models' or 'list_integrations', which would require mentioning it fetches a single integration by identifier rather than listing or getting related models.

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. For example, it doesn't mention that 'list_integrations' should be used for browsing all integrations or 'get_integration_models' for related models, leaving the agent to infer usage from context alone.

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