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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint and openWorldHint, so the safety profile is fully handled by structured data. The description adds one genuinely new behavioral fact — 'Free' — meaning no billing consequence, which is useful but is the only 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?

Two short fragments, no filler, with the cost note and the usage rule front-loaded. It is efficient, though the middle noun list is a little unparsed and could have been tied to the topic values.

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 single-optional-parameter, read-only documentation tool with a full output schema and rich annotations, the description covers what it is, its cost, and when to consult it. Nothing essential to correct invocation 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?

Schema description coverage is 100% and the enum's default is already documented in the schema ('overview is the default'). The phrase 'Rules, prices, recipes, and filters' loosely maps to some topic values but does not add syntax, format, or selection guidance beyond what the enum already provides, so the baseline 3 applies.

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 (the guide) and enumerates its contents — rules, prices, recipes, filters — which tells an agent what it will get back. The verb 'read' is only implicit and the framing is telegraphic, but the topic enumeration clearly separates it from siblings like get_list or list_billing_transactions.

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?

It gives explicit sequencing guidance: 'Read overview before the first search and costs before spending.' That tells the agent when in a workflow to call this. It stops short of naming alternative tools or stating when not to call it, so it is 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.