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

Annotations already cover read-only/idempotent/non-destructive, and the description adds real value beyond them by disclosing that names are snapshot-dated and that naming, regions and pricing must be re-verified before deciding. That is a meaningful freshness/accuracy warning an agent would not otherwise see.

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 filler, with the core operation front-loaded and the caveat trailing where it belongs. Nothing repeats the schema or annotations verbatim.

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?

An output schema exists, so return values need not be described, and the freshness caveat is handled well. However, for a 4-parameter tool with zero schema documentation, the description leaves key inputs (query, categories, multi-target 'to') unexplained, which is a meaningful gap.

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 description coverage is 0% across 4 parameters, so the description must carry the burden and does not: the roles of 'from' vs 'to', the default of 'from' to aws, the array semantics of 'to', and especially what 'query' and 'categories' mean are never explained. Only the cloud list (including 'open source' ↔ 'oss') is implicitly reflected.

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 (map) and resource (cloud capability → equivalent managed services) and enumerates the target clouds. It is clear what the tool produces, but it never distinguishes itself from the close sibling service_compare, so an agent must infer which to pick.

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?

The second sentence is a staleness/pricing caveat, not usage guidance: it never says when to reach for this tool versus service_compare, nor what input shape (free-text capability? category?) is expected. No exclusion or alternative is named.

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