amber_current_price

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds only that the result is a 'current price' and scoped to a site; it says nothing about auth requirements, error behavior, or return shape 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?

A single efficient sentence with the resource and qualifier front-loaded. No waste, though it could carry one more clause of routing/param context at little cost.

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 getter with no output schema, the description is close but leaves the two parameters (especially api_key and where site_id comes from) undocumented. A brief note on obtaining site_id would complete it.

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 0% and the description explains neither parameter. The required site_id has no format or source guidance (presumably from amber_sites), and the api_key parameter is completely unexplained despite being an auth-sensitive input.

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?

States a specific verb ('Get') and resource ('current electricity price for an Amber site'). The word 'current' implicitly distinguishes it from amber_forecast, but it does not explicitly name that sibling or amber_sites.

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?

Usage is only implied: 'current' suggests now-vs-forecast, and 'for an Amber site' implies you need a site already known. No explicit when/when-not or alternative routing (amber_forecast for future prices, amber_sites to discover sites).

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