List OCI Edge services such as DNS, Email Delivery, and Health Checks, filtered by service type. Deprecated: use list_services_by_category instead.
[DEPRECATED: use list_services_by_category with category="edge"] List OCI Edge services including DNS, Email Delivery, and Health Checks.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Filter by edge service type |
Changes observed during successful MCP inspections.
v1.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds deprecation status and scope of services (DNS, Email Delivery, Health Checks), which is valuable context beyond annotations.
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, front-loaded with deprecation notice. No wasted words. Efficient and clear.
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 read-only list tool with one optional parameter and no output schema, the description is sufficient. Deprecation notice and service types cover all needed context.
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?
Input schema covers 100% of parameters with clear descriptions and enums. Description lists the service types in prose, reinforcing schema but not adding new meaning. Baseline 3 with marginal value added.
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?
Description clearly states it lists OCI Edge services (DNS, Email Delivery, Health Checks) and explicitly deprecates itself, pointing to list_services_by_category as alternative. Verb 'list' and resource are specific.
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?
Explicitly says '[DEPRECATED: use list_services_by_category with category="edge"]' providing clear guidance to avoid this tool and use the alternative. No ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.