ozon_order_fbo_get

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It gives no indication of whether this is read-only, what data it returns, whether it can fail, or any side effects. The only meaningful behavior 'get details' is implied by the tool name, not the description.

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 extremely short, but this is under-specification rather than efficient conciseness. It contains only a noun phrase with no helpful structure, no context, and no guidance. It earns credit for being brief, but not for being appropriately informative.

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?

For a single-parameter get-details tool with no output schema and no annotations, the description is woefully incomplete. It fails to specify what details are returned, how FBO posting numbers should be obtained, or how this tool differs from the many related order and FBO tools in the sibling list.

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 input schema has one parameter, posting_number, with no description (0% schema coverage). The description does not explain what posting_number represents, its expected format, or how it relates to FBO postings. The description adds no semantic value beyond the bare parameter name.

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 'FBO posting details' essentially restates the tool name without a clear verb or scope. It conveys that the resource is an FBO posting but does not explicitly state that it retrieves details, nor does it distinguish it from similar tools like ozon_orders_fbo or ozon_order_fbs_get.

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 use this tool versus alternatives. No mention of prerequisites, filtering options, or relationship to other order-related endpoints. The agent is left to infer the use case 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.