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

The readOnlyHint annotation already establishes this is a safe, non-mutating read, so the bar is lower. The description adds that the payload is reference material spanning facts, syntax, presets, and pricing, and 'current pricing' hints at dynamic values, but it says nothing about format, size, or whether presets/pricing change over time.

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 front-loaded phrase with no filler, listing four distinct content sections. It is a noun phrase rather than a sentence, but every element earns its place and nothing is padded.

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 usefully enumerates what the payload contains, which covers the basic need. It stops short of explaining how these facts relate to gate's rule evaluation or how a caller should consume the syntax section, leaving the agent to infer the workflow.

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; there is nothing for the description to disambiguate at the argument level. It could still note that the entire catalog is returned unconditionally, but that is implicit in an 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?

The description inventories concrete contents: fact names/types/meanings usable by policy rules, rule syntax, presets, and current pricing. That is specific enough to tell this is a reference/catalog tool rather than an evaluator like gate or gate_batch, though it lacks an explicit verb ('returns') and never names the siblings it complements.

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?

There is no when-to-use guidance: nothing says to call this before composing a policy for gate, or that it is the lookup companion to gate/gate_batch. The reference nature implies usage, but no condition, prerequisite, or alternative is stated.

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