ozon_check_auth

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

Annotations already declare readOnlyHint=true, but the description adds valuable safety context beyond that: it explicitly states that secret values are NOT revealed and only variable presence is reported. This helps the agent avoid mishandling sensitive data and matches the read-only annotation.

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?

Three short, purposeful sentences: the core purpose, a critical safety caveat, and the exact return shape. No filler or repetition; information is front-loaded and easy to parse.

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 simplicity—no parameters, read-only annotations, and explicit return JSON in the description—the definition fully covers what the agent needs to call and interpret the tool. Nothing important 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?

The tool has zero parameters, so there is nothing for the description to clarify. The schema is effectively complete at 100% coverage, and the description's mention of the missing/required arrays provides useful context for interpreting results.

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 states a specific action and resource: 'Check whether the required credentials are present in the environment.' This clearly differentiates it from sibling tools that perform data operations or key management, since no other sibling is an auth-check diagnostic.

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 intended use is implied: call this tool to verify credential presence before attempting authenticated Ozon operations. However, the description never explicitly says 'use before other Ozon tools' and does not mention alternatives or exclusions, leaving the timing to inference.

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