pm_buy_order

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

No annotations are provided, so the description must fully disclose behavior. It only states 'fill' without mentioning side effects, permissions, or state changes. The agent lacks information on whether this is a mutation or read operation.

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 a single, short sentence. While concise, it is under-specified and lacks necessary detail, reducing usefulness. Conciseness should not come at the cost of clarity.

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?

With three required parameters, no output schema, and no behavioral hints, the description is severely incomplete. It does not explain the result of 'fill', order lifecycle, or error conditions.

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% (no parameter descriptions in schema). The description adds no meaning to the three required parameters (market, order_id, amount_usdb). It fails to explain what each parameter represents or how they are used.

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 'Fill a private market order' states a verb and resource, distinguishing privacy from public orders via the term 'private'. However, it does not differentiate from sibling tools like 'pm_buy' or 'pm_buy_multiple_orders', lacking specificity in scope.

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?

No guidance on when to use this tool versus alternatives (e.g., public 'buy_order' or other pm_ variants). No context about prerequisites or conditions for private market orders.

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