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

Annotations already establish readOnly, idempotent, open-world, non-destructive. The description adds genuinely new behavioral context beyond that: the data reflects a 'current' tariff version and prices must not be cached as permanent knowledge, telling the agent the payload is time-sensitive. It stops short of describing the shape or size of the returned data.

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 short sentences with no filler, and the subject of the catalog is front-loaded. The first sentence is a fragment rather than a complete statement, which slightly weakens the front-loading.

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 tool with no output schema, the description is minimally adequate: it hints at contents ('resources and rules') but never says what a returned catalog actually contains or how to consume it. The freshness caveat helps, but an agent still has to discover the response shape by calling 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 rubric the baseline is 4. The description has no parameter behavior to explain and correctly adds none.

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 names the resource domain (tariff version, resources, rules) but is a noun fragment with no verb, so it never states that it retrieves/returns the catalog. An agent can partially distinguish it from calculate_quote or get_events from the subject matter, but the action itself is only implied.

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 and no mention of alternatives, despite calculate_quote being an obvious sibling that consumes tariff data. The only directive is a caching caveat, which is operational advice rather than selection guidance.

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