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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the call neither starts a model call nor charges the wallet, which tells the agent the operation is cost-free and side-effect-free — a useful addition beyond the 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?

Three short sentences, front-loaded with the action and its cost/effect profile, with no filler. The final pseudo-imperative ('Check enabled and scope before quoting') is slightly terse and underspecified, but it is not wasted text.

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 zero-parameter, read-only, closed-world tool with no output schema, the description covers the essentials: what it reads, that it is billed/no-cost, and the pre-quote prerequisite. It does not describe the shape of the returned target list, but the lack of an output schema makes that a minor gap for an agent deciding whether to call 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?

The tool takes zero parameters, so per the baseline rule this scores 4; there is no parameter surface the description needs to explain. Nothing in the description contradicts or muddies the empty 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?

States a specific verb+resource ('Read current GEO target availability and pricing') and the auth context ('configured API Key'). It is distinguishable from geo_quote_observation by framing this as the availability/pricing read step, though it never names that sibling, so the differentiation is inferred rather than explicit.

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?

'Check enabled and scope before quoting' implies this is a pre-quote check and hints at a prerequisite, which is useful. However, it does not name geo_quote_observation as the alternative or state when NOT to call this tool, so the routing guidance stays implicit.

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