ozon_list_methods_for_subscription

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tier filter is auto-extracted and may not match actual 403 sets, which adds transparency. However, it does not mention read-only nature, authentication needs, or rate limits, though these are partially implied by the tool name.

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 two short paragraphs, front-loading the purpose. The docstring-style argument list is clear. Minor redundancy in the example use cases but overall 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?

Given the presence of an output schema and the simplicity of the tool (single parameter), the description is complete. It covers purpose, usage scenario, parameter constraints, and a caveat about accuracy. No further details are needed.

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 0%, so the description must explain the parameter. It lists the five possible values for 'tier', which adds meaning beyond the schema's type definition. It could further explain what each tier represents, but the list is sufficient.

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 'List all Ozon methods that mention a specific subscription tier,' providing a specific verb and resource. It distinguishes from siblings like ozon_get_subscription_status and ozon_search_methods by filtering by tier.

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 includes explicit use cases ('want to know what extra capabilities do I unlock by upgrading?') and notes the limitation that it's a hint, not a contract. It lacks explicit when-not-to-use or alternatives, but the guidance is clear.

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