Estimate monthly Oracle Cloud Infrastructure costs for common deployment presets like small-web-app, medium-api-server, large-database, ml-training, and kubernetes-cluster.
Get a quick cost estimate for common deployment presets: small-web-app, medium-api-server, large-database, ml-training, kubernetes-cluster.
| Name | Required | Description | Default |
|---|---|---|---|
| preset | Yes | Deployment preset | |
| region | No | OCI region |
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, destructiveHint, idempotentHint. The description adds the preset scoping but no new behavioral traits like caching or region defaults.
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?
Single, efficient sentence with no wasted words, listing all presets inline.
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?
No output schema, but description does not mention return format or example. Adequate for a simple tool but not fully complete for an agent.
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 coverage is 100%, so baseline is 3. The description lists presets already in the enum, adding no new meaning beyond the schema.
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 tool provides a 'quick cost estimate' for listed presets, distinguishing it from more detailed sibling calculators like calculate_database_cost.
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 on when to use this tool vs alternatives (e.g., calculate_database_cost). The description only implies it's for quick estimates but does not explicitly exclude other tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.