manifest_placeLimitOrder

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

The description lacks any disclosure of behavioral traits such as order matching mechanics, reversibility, or fees. With no annotations, the agent has no insight into the tool's mutability or confirmation requirements.

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 very short but earns its place as a single sentence. However, it lacks structured sections for clarity and omits necessary details, making it insufficiently informative despite conciseness.

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, the description should indicate return values or confirmations, but it does not. The tool is a trading operation with 6 parameters, yet the description fails to provide enough context for correct invocation.

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 description adds no additional meaning beyond the input schema. While schema covers 4 of 6 parameters with descriptions, the 'side' and 'orderType' enums are not explained, leaving ambiguity about their effect.

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 action 'Place a limit order' and the specific platform 'Manifest market', effectively distinguishing from sibling tools like manifest_cancelOrder. However, it does not differentiate from other limit order tools across platforms.

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 guidelines are provided on when to use this tool versus alternatives like openbook_placeOrder or jupiter_createLimitOrder. Prerequisites, side effects, or conditions are absent.

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