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

Annotations already declare readOnlyHint=true, and the description reinforces that ('Read-only'). Beyond annotations it discloses genuinely useful behavior: the exact fallback defaults returned when nothing was ever configured (eur, 0, egress off, limit 8), which an agent cannot infer from the schema or 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?

The primary purpose is front-loaded in the opening clause, and the long appositive list of fields is dense but each clause carries real information. The trailing 'Read-only; read this before update_cost_settings' is terse and earns its place, though the middle sentence is heavy.

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?

With no output schema, the description carries the full burden of documenting return values and does so: it enumerates all four settings, defines the allowed currency values, explains what the discount approximates, and gives the exact defaults. Nothing needed to interpret the result is missing.

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?

The tool takes zero parameters, so the baseline is 4. The description instead spends its detail on output-field semantics (what currency, discount, egress and analysed_cluster_limit mean), which is beyond the input schema but not parameter-focused.

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?

Specific verb ('Get') plus a precisely scoped resource ('the organisation's cloud cost pricing settings'), followed by an enumeration of the exact settings returned (currency, discount, egress, analysed_cluster_limit). It also names the related sibling update_cost_settings, so an agent can place it immediately among the many get_* tools.

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 states this is read-only and directs the agent to 'read this before update_cost_settings', giving a clear ordering relationship and an implicit alternative (the write path). It stops short of stating when-not to use it (e.g. versus get_billing_standing or get_fleet_cloud_cost), so not a full 5.

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