city_fee_rule

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the trailing 'Read-only' sentence merely restates structured data without adding anything. No added context is given on the fee rule model, whether results are cached, or when rules change.

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 the core purpose front-loaded and no padding. However, the second sentence duplicates the annotations rather than earning its place, so it is not maximally efficient.

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?

Because an output schema exists, the return format need not be described, and the read-only nature is covered by annotations. The remaining gaps are the undocumented city_id and the absence of any usage context, which leaves the definition at a minimal-but-adequate level.

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 only parameter, city_id, has 0% schema description coverage and the description never mentions it, so there is no guidance on where the city id comes from or its expected scope. With one undocumented required parameter, the description fails to compensate for the schema gap.

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 gives a specific verb+resource ('Return fee/fare rules for a city'), which is clear enough to distinguish from siblings like current_ride or pass_catalogue. It stops short of explicitly differentiating itself from any sibling, but the resource is distinct within this API surface.

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 guidance on when to call this versus other sibling tools, no prerequisites, and no mention of how it relates to ride_order or account_month_amount where fees might also surface. The agent is left to infer usage entirely from the name.

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