block_delivery_sell_order

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

With no annotations, the description discloses a critical behavior: the order is never sent to the broker and requires manual verification. This goes beyond the input schema, though it could mention side effects like data storage or return value. The key behavioral trait is well communicated.

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?

Two sentences with no wasted words. The first sentence delivers the core purpose, and the second adds essential behavioral context. Perfectly concise and front-loaded.

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 no output schema or annotations, the description covers the key behavioral constraint (no broker submission). It lacks mention of return value or prerequisites (e.g., symbol validity). Still, it provides sufficient context for a simple recommendation-recording tool.

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%, and the description adds no explanation for parameters (symbol, quantity, reason). Parameter names are self-explanatory, but the description fails to compensate for the lack of schema descriptions. At minimum, it should clarify the role of 'reason' (e.g., optional note).

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?

Description clearly states the verb 'Record' and resource 'delivery-sell RECOMMENDATION', distinguishing it from execution tools like execute_delivery_buy_after_validation. It specifies that the order is never sent to the broker, making the purpose unambiguous.

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 implies usage for recording recommendations, contrasting with actual execution tools. It clearly indicates this is not for live orders, but lacks explicit when-not-to-use or alternative tool names. The context is clear enough for an agent to infer appropriate usage.

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