guarded_place_order

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

Annotations indicate non-readonly and non-idempotent. Description adds key behaviors: mandatory pre-flight check, budget persistence via local ledger recording, and structured error response. No contradiction with annotations.

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, well-structured paragraph with front-loaded purpose, followed by constraints, error behavior, persistence, and return format. Every sentence adds value without redundancy.

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?

Covers core behavior and return structure but lacks context about dependencies (e.g., need to set limit via guard_set_limit) and does not explain edge cases for parameters like limitPrice. Given no output schema, the return structure is described but informally.

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 has 50% parameter description coverage (3 of 6 parameters described). The tool description does not add any parameter-specific meaning or clarify missing descriptions, leaving ambiguity about side, type, and tif.

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 the tool's action ('Place an order on Alpaca') with a specific condition regarding daily budget cap, distinguishing it from siblings like guarded_close_position. It uses specific verbs and resources.

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?

Explicitly states when to use ('Pre-flight is mandatory') and what happens if budget exceeded (BUDGET_EXCEEDED). Does not explicitly mention when not to use or alternative tools, but context from siblings implies it's the execution tool after setting a limit.

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