get_aws_price

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

Describes return values (vCPUs, memory, hourly USD, monthly USD) and constraints (on-demand Linux, us-east-1). Lacks explicit mention of read-only nature or any side effects, but no annotations to contradict; behavior is well disclosed.

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, no wasted words. First sentence conveys purpose and output, second gives alternative. Front-loaded with key action.

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 simple tool with one parameter and no output schema, description fully covers purpose, return fields, constraints, and alternative. No gaps for effective use.

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 covers 100% of parameter, but description adds context that the instance_type is for on-demand Linux in us-east-1, enhancing meaning beyond the schema's type listing.

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?

Clearly states the verb 'Look up' and specific resource: on-demand Linux hourly and monthly price for AWS EC2 instance type in us-east-1. Distinguishes from sibling compare_clouds by focusing on single AWS instance pricing.

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 specifies when to use (on-demand Linux, us-east-1) and provides an alternative (use compare_clouds for multi-cloud comparisons). Clear context.

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