ozon_get_rate_limits

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

With no annotations provided, the description discloses that many limits are conservative guesses (source: 'guess') and advises verification in production. It also explains the override hierarchy. This provides important behavioral context beyond the basic function.

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?

The description is concise with five sentences that efficiently convey purpose, default behavior, argument-specific behavior, and a critical caveat. No extraneous information.

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?

Given the tool's low complexity (2 optional parameters, output schema exists), the description adequately covers the key aspects: default behavior, override logic, and data quality warning. It does not mention potential errors or rate limit format, but the output schema likely covers return values.

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 coverage is 0%, so the description must add parameter meaning. It explains that without arguments returns all limits, and with operation_id returns specific limits, implying operation_id's role. However, it does not explicitly describe the 'section' parameter, leaving its purpose somewhat ambiguous.

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 clearly states the tool's purpose: 'Look up rate limits for a method, section, or the whole API.' The verb 'look up' and resource 'rate limits' are specific, and the tool is distinct from siblings like ozon_call_method or ozon_describe_method.

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?

The description explains behavior without arguments (returns all limits) and with operation_id (returns most specific limit via override hierarchy). It also includes a caution about conservative guesses and advising verification in production, guiding appropriate use. However, it does not explicitly mention when to use section vs operation_id or alternatives.

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