ozon_get_subscription_status

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

Discloses caching (per process, refreshable, errors never cached) and credential requirement. No annotations exist so description carries burden. Lacks mention of idempotency or rate limits, but acceptable for a read-only tool.

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?

Four concise sentences, front-loaded with main purpose, no redundant words. Each sentence adds distinct 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?

Tool is simple (1 param, no required ones) and has output schema. Description covers purpose, input, caching, prerequisite, and output content. Complete for reliable agent usage.

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?

With 0% schema coverage, description explains the sole parameter 'refresh': 'pass refresh=True to bypass cache'. Adds practical meaning beyond schema's default.

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?

Clearly states the verb 'get' and resource 'subscription tier' from a specific endpoint. Specifies return values (type, is_premium flag, list of methods). Distinguishes from sibling tools like ozon_list_methods_for_subscription.

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?

Provides context: prerequisite (seller credentials), caching behavior, and refresh bypass. Does not explicitly exclude scenarios or compare with alternatives, but sufficient for most cases.

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